Bug#581606: NMU of pinball
Hello Matthias, a 0-day NMU for a quite recent bug report is quite rude from the maintainer POV, in particular because you didn't ping the bug neither you post a patch on the bug report (as required by devref) and you didn't upload to a DELAYED queue, giving time to the maintainer to react. Funny how the MU came only minutes after your NMU, another sign of un-coordinated NMU. Please give a look at http://www.debian.org/doc/developers-reference/pkgs.html#nmu for an overview of NMU procedures. Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#581606: NMU of pinball
Hi Sandro, a 0-day NMU for a quite recent bug report is quite rude from the maintainer POV, in particular because you didn't ping the bug neither you post a patch on the bug report (as required by devref) and you didn't upload to a DELAYED queue, giving time to the maintainer to react. Funny how the MU came only minutes after your NMU, another sign of un-coordinated NMU. If you have a look at http://wiki.debian.org/LowThresholdNmu, you'll see that I accept this sort of NMU for all packages except for the net-snmp one (here I just require anyone to resgister as co-maintainer and add the package to SVN first, BTW. Otherwise, the history in SVN becomes a mess). In this case I was just preparing to fix a piupart error and finally decided to push it out now that a RC bug was rised. I don't think this NMU caused a lot of work on Matthias ;-) Thanks, Jochen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#581606: NMU of pinball
Hello Jochen, thanks for your reply. On Tue, May 18, 2010 at 12:38, Jochen Friedrich joc...@scram.de wrote: Hi Sandro, a 0-day NMU for a quite recent bug report is quite rude from the maintainer POV, in particular because you didn't ping the bug neither you post a patch on the bug report (as required by devref) and you didn't upload to a DELAYED queue, giving time to the maintainer to react. Funny how the MU came only minutes after your NMU, another sign of un-coordinated NMU. If you have a look at http://wiki.debian.org/LowThresholdNmu, you'll see that I accept this sort of NMU for all packages except for the net-snmp one (here I just require anyone to resgister as co-maintainer and add the package to SVN first, BTW. Otherwise, the history in SVN becomes a mess). In this case I was just preparing to fix a piupart error and finally decided to push it out now that a RC bug was rised. I don't think this NMU caused a lot of work on Matthias ;-) that doesn't change the fact there are some rules for NMUs, and one of them is posting the diff to the BTS, that didn't happen (and uploading to DELAYED/2 would be nice). Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
