Re: Bug#449497: foo2zjs dispute

[Andreas Barth <aba@not.so.argh.org>]

# please read it till the end before flame!
# speaking with my TC hat on
severity 449497 important
thanks

* Steffen Joeris (steffen.joeris@skolelinux.de) [081031 14:31]:
> Dear Technical Committee Members
> 
> Currently, there is a dispute about a certain part of the foo2zjs package. 
> Unfortunately, we do not seem to be able to solve it and thus require your 
> assistance. We have tried to get a paragraph together to state the problem, 
> but it seems we ended up with two different paragraphs. The first one is from 
> the maintainer (myself) and the second one belongs to the bug submitter 
> (Michael Gilbert). Could you please pass your judgement on this case?
> You will find further information in the bugreport and I am sure that the 
> submitter as well as the maintainers are happy to answer any follow-up 
> questions. At the moment, the bug is marked as RC, which might have an impact 
> for the lenny release.
> Thanks in advance for your time and judgement.

I think that the proper way to determine the severity of a bug report
is:

1. The submitter sets an initial severity (done)
2. The maintainer(s) decide on the severity (they seem to have decided
that this isn't release critical, lowering the severity to important as
per decision of the maintainers)
3. The release team can review the decision as above and change the
severity if necessary (not done)
4. As last instances, both the tech ctte and the developers together by
an GR could make a decision that changes the severity again and overrule
the appropriate delegates decisions.

(Just to note: Normally anybody can adjust the severity, and that's a
feature. However, if things get more heated, it's vital that we don't
play bts ping-pong, but relax and let the appropriate people make their
decision.)


As the release team who regularly reviews the bug severities didn't do
any decision yet, I think they should decide first before calling up to
the tech ctte. (Also, please note that due to a spelling mistake this
bug didn't get reassigned yet.)


So, how to continue: If someone continues to disagree with the decision
of the maintainers on the bugs severity (as stated above), feel free to
call in the release team to get their (perhaps different from the
maintainers) decision. If someone isn't satisfied with the release teams
decision, the tech ctte can be asked later on. If still not satisfied,
the rules of GRs are written down in the constitution.

However, please DO NOT change the bug severity (except of course by
the maintainers of the package, or the release team, or the tech ctte or
the secretary after an GR, or the owners@bugs).



Cheers,
Andi