Re: Disputes between developers - draft guidelines
* Branden Robinson <email@example.com> [021017 00:51]:
> > In particular, I note that you seem to be grinding your axe about the
> > issue from Bug#97671.
> No, you do me a disservice. That was not Debian's first severity war
> and it probably won't be the last.
For new Developers the text might provide useful in their first
ploddings around the BTS when they come across a paticularly nasty bug
that is either hampering their package work and/or their work at a job.
Some people initially think that the severities are really a great tool
to gain priority if their defect matches (however vaguely) a list of
standards. I would suggest that the documentation definately allows a
reporter to set a severity as an initial suggestion, but leaves it after
that point up to the developer. Obviously, RC-ness of any bug
regardless of severity should be left up to the Release Manager.
I'm saying this after being in at least one stupid flip-flop where I
really didn't feel good about my actions after I really realised what
the deal was.
> I would not presume to trump the authority of the BTS admins, to the
> extent that they choose to exercise it. However, they probably wouldn't
> like to make decisions in a vacuum, so I have offered my perspectives on
I also agree. I would think the BTS admins would like this to be agreed
upon in a social sense of etiquette rather than from upon high.
Scott Dier <firstname.lastname@example.org> KC0OBS http://www.ringworld.org/
"Many voters assume that their political leaders are hard at work on
these issues. They are not."
_Editorial: Time to choose / Who will deliver on transportation?_