[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#455769: same problem on wheezy + Thinkpad X220T

On 02/04/13 19:57, Ian Jackson wrote:
> Vincent Bernat writes ("Re: Bug#455769: same problem on wheezy + Thinkpad X220T"):
>>  ❦ 28 mars 2013 20:38 CET, Thomas Goirand <zigo@debian.org> :
>>> Unless you are the original reporter and you need to
>>> decide in order to fill the bug, please don't. That's the
>>> role of the maintainer to do that triaging work (as
>>> already stated multiple times!).
>> We encourage people to help triaging. Setting the appropriate severity
>> is part of the work. I have never read that setting severity can only be
>> done by the maintainer. The only consensus against this is when the
>> severity is changed several times.
> I agree.  But such triage should be done in a way that the maintainer
> will agree with.  Fighting with the maintainer's view of severities is
> not "triage", it is abuse.

Personally, I feel there is a distinction between fighting and debating
a viewpoint, and those who are willing to invest the time and effort in
troubleshooting, documenting and solving issues should not be afraid to
discuss any relevant aspect of a bug, including the severity, in the
right manner and with the best intentions.

I realise I've personally had some confusion with this and caused some
people frustration, and I apologise if my style is sometimes too terse
or having the wrong impact.  In one case, Thomas appears to have the
felt that I had raised the severity of one bug twice[1] (in fact, I only
did so once, but on two different bugs, for independent reasons, one of
which involves losing all network connectivity[2]).  In both of those
cases, I feel I've tried to be part of the solution, contributing
analysis and workarounds, because I think the maintainer and upstream
have done a great job bringing those rather complicated packages to
Debian; it would be a shame to risk putting out a stable release that
doesn't include fixes for issues that appear to be quite acute but also
trivial to fix within a timeframe that is reasonable given the freeze

1. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=702428#24

2. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=695221

Reply to: