On Fri, 24 Oct 2014, Jakub Wilk wrote: > But anyway, this workflow seems completely reasonable to me: > 1) upload to mentors.d.n; > 2) have someone review the changes; > 3) have someone commit to upload the NMU; > 4) file a bug (or post to existing bug) stating your intention to NMU. > > This is how I did NMUs before I was a DD, and this is how I expect > non-DDs to NMU my packages.
To avoid wasted work, I suggest that we recommend this, instead: [for NMUs made through debian-mentors]: 1) add a notice to the relevant bug reports in the BTS stating that you are preparing an NMU through debian-mentors (if there is no such a bug, open one. You will reuse it for step 5. Title it "<package>: intent to NMU: <reasons for the NMU>"). 2) upload to mendors.d.n. 3) have someone review the changes, repeat steps 2 and 3 as necessary 4) have someone commit to upload the NMU 5) file the NMU bug (if you had to create a bug report in step 1, reuse it. Retitle it to follow the procedure for NMU bugs). Seems friendly enough to all involved... -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141024134740.gd23...@khazad-dum.debian.net