On Fri, Oct 25, 2019 at 3:45 AM Nathan Cutler <ncutler@xxxxxxxx> 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]. > > (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 don't understand why we want to special-case one backport. It's usually confusing to have two PRs cited in a tracker as that's a catalyst for wrong backports. For example, what if Mimic is added at a future time when the backport is realized as necessary; this happens fairly frequently. We already have automation (scripts) which make this pretty easy so I don't see a point. I'd vote we don't do this. -- Patrick Donnelly, Ph.D. He / Him / His Senior Software Engineer Red Hat Sunnyvale, CA GPG: 19F28A586F808C2402351B93C3301A3E258DD79D _______________________________________________ Dev mailing list -- dev@xxxxxxx To unsubscribe send an email to dev-leave@xxxxxxx
