Steve Langasek <vor...@debian.org> writes: > RC bug severity has an important function in blocking package migrations > to testing. If someone is concerned that a particular regression in > behavior is sufficiently severe that it should block the new version of > the package from testing, they certainly should set the bug severity in > the first instance.
Ah, sorry, yes. This is a good point that I neglected. The RC severity discussion is perfectly fine if one is worried about impact on testing for exactly the reasons you state. That said, it's still not a good reason to try to get something into Policy, or a good way of starting a Policy discussion. (Among other things, it's not the role of Policy to determine RC severity. That's the call of the release team, although they will certainly take existing Policy consensus into account.) Policy is about figuring out what the right thing to do is, but can't allocate resources, and is too slow to be the place to control whether things migrate to testing. -- Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/87mwend2vs....@windlord.stanford.edu