Hi Lenz, On Wednesday, February 19, 2020 1:48 PM, Lenz Grimmer <lgrimmer@xxxxxxxx> wrote: > Hi Benoît, > > On 2020-02-19 08:04, Benoît Knecht wrote: > > [...] > > > > What would be the best way forward in this case? Submit a PR without a backport tracker issue? Manually create the backport issue? > > According to > https://github.com/ceph/ceph/blob/master/SubmittingPatches-backports.rst#tracker-workflow > it's fine to create a tracker issue "after the fact": "f the master PR > has already been merged and there is no associated master tracker issue, > you can create a master tracker issue and fill in the fields as > described below." > > So the steps are: > > 1. create a tracker issue and get the status set to "Pending Backport", > adding "nautilus" to the "Backport" field. > > 2. Wait for the backporting team to create the corresponding backport > tracker issue. > > 3. Submit your backport PR and reference it in the backport issue Thank you very much for your answer, and shame on me for not reading the backport guidelines carefully enough :\ I'll follow those steps then! Cheers, -- Ben _______________________________________________ Dev mailing list -- dev@xxxxxxx To unsubscribe send an email to dev-leave@xxxxxxx
