We've been discussing this @FOSDEM too. My suggestion was that any bug that visibly hurts stable users should always be considered at least MAJOR in bugzilla.
To expand on this a bit more * a stable update that makes the computer nonfunctional is definitely BLOCKER (and should be reverted in CVS immediately when it becomes known, at latest when it is understood, by anyone who is around at the time and can do so) * a non-functional stable package in the system set should be CRITICAL. Just my 2ct, but it is really important not to hurt stable users. This is how we lose most people. > I think that maybe we could have an even higher "priority" field called, > for example, "Broken Stable" that should be *only* used for that cases > and that arch teams should try fix sooner. What do you think? -- Andreas K. Huettel Gentoo Linux developer dilfri...@gentoo.org http://www.akhuettel.de/
signature.asc
Description: This is a digitally signed message part.
