Hi Nathan, On 10/25/19 12:45 PM, Nathan Cutler wrote: > Hi all, there seems to be some confusion concerning the backport tracker. > > The purpose of the backport tracker is to track backports of fixes that need to > go into multiple stable branches, so they don't "fall through the cracks". > > If you need to backport something from master *only* to nautilus *and no > farther*, there is no need to create tracker issues for backporting purposes. > Just open your nautilus PR with the cherry-pick [1]. This is news to me. Has this policy been changed recently? What was the rationale do change it? I remember I reviewed that chapter, but somehow missed that particular detail. > (If there is already a master tracker issue, you can just mention the URL of the > nautilus backport in a comment on the tracker. You don't need to change the > status to Pending Backport or fill in the Backport field.) I have to agree with Patrick that I find this confusing and more error prone. Why making that exception? If a backport is needed, a corresponding tracker issue should be created. Thanks, Lenu -- SUSE Software Solutions Germany GmbH - Maxfeldstr. 5 - 90409 Nuernberg GF: Felix Imendörffer, HRB 36809 (AG Nürnberg)
Attachment:
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Dev mailing list -- dev@xxxxxxx To unsubscribe send an email to dev-leave@xxxxxxx
