On Sat, Dec 27, 2008 at 04:11:35PM +1100, Ben Finney wrote:
> The decision of whether a bug is release-critical or not is for the
> release managers to make, using the various properties of the bug
> (including but *not* limited to its severity) as input to that
> decision. They can, in fact, make that decision apparent in the bug
> report *without* altering the severity level.
At the last Extramadura meeting, talking with Dato (Cc-ed) and some
other fellows, we identified the (potential) need for the Release Team
to have a sort of "override" file for the severities of bug reports
and, more generally, of all bug-related information.
( The argument which led to that was kinda bogus, it was something
like: "given that we make decisions on the basis of the BTS, and
given that the latter is completely open, we _might_ need to protect
ourselves letting the RMs have the last word on what a bug
information really is". After all RMs already have various kind of
overrides which affect britney's run, that would have been just
another, more fine grained, override )
The reason why I'm reporting it here is that such a tool would also
enable to address needs such as the reported one: wishlist bug report,
marked with some RC-severity in the override.
I'm not claiming it would be a clean solution, I just got surprised
that the very same tool can address both needs.
Cheers.
--
Stefano Zacchiroli -o- PhD in Computer Science \ PostDoc @ Univ. Paris 7
zack@{upsilon.cc,pps.jussieu.fr,debian.org} -<>- http://upsilon.cc/zack/
Dietro un grande uomo c'è ..| . |. Et ne m'en veux pas si je te tutoie
sempre uno zaino ...........| ..: |.... Je dis tu à tous ceux que j'aime
Attachment:
signature.asc
Description: Digital signature