On 03/28/2013 06:47 PM, Daniel Pocock wrote: > On 28/03/13 11:06, Julien Cristau wrote: >> Control: severity -1 important >> >> I am raising this bug to critical, as it meets the definition "makes >> unrelated software on the system (or the whole system) break" >> No, it does not. hw will shut itself off before getting damaged. > Would you provide a guarantee to all users of wheezy that you will pay > for their laptop repair if this issue causes damage? > > Having the hardware shutdown like that is also a nasty thing that > involves the user losing unsaved work, maybe corrupting preferences for > their desktop if they are unlucky. > > This problem happens regularly enough that Debian should not be promoted > for laptops if it is not taken seriously as an RC issue. Users will get > a very bad impression if basic things like this aren't working in a > stable release. > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=455769 Daniel,
This isn't the first time that you are discussing the severity of bugs, and raising them to RC level instead of what they deserve, which was the original severity. You did that to some of my packages (for example, see #695221, for which my upload of the fix is by the way overdue...). It seem to me that you believe only RC bugs can be fixed in the (next) stable distribution. This reasoning is wrong. The release team has by the way confirmed this. I did already fixed many non-RC bugs in Wheezy, and the release team has accepted them. There are hundreds (thousands?) of such examples. There was no problem with it. I am also quite positive that it is possible to fix bugs in the stable distro, by using stable-proposed-updates (I did that when fixing the RTC clock in the Xen hypervisor thanks to a patch from upstream, just to take an example from the back of my mind). I'd like to kindly tell you that such BTS ping-pong is completely pointless. Raising the severity of bugs will have absolutely zero effect. It will not help to find the problem, and it will not help to fix it either. Finally, it is up to the package maintainer to have the final decision (or even, up to the release team) about the severity of bugs. The fact that you find a particular bug quite annoying, or affecting you, doesn't change that fact. What is important to keep in mind with severity of bugs, is the definitions which are provided by reportbug when you first report a bug. Please re-read them again. If you want a bug to be fixed fast, well... try fix it yourself, that is the best way forward! So, Daniel, please learn from this, and don't try raising severity of bugs again. The only effect is that you may piss-off some of the maintainer(s) and maybe even the release team (I was ok when you did it with me, but maybe some other people might find it rude...). That being said, you are very welcome to contribute any information you may have in the BTS. Even a "me too", to confirm that you have the problem and that this isn't an isolated case, is helpful. Thanks for your contributions in Debian, Cheers, Thomas Goirand -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/51545e5f.50...@debian.org
