On 2013-04-02 14:17:17 +0100, Neil Williams wrote: > The release happens when (almost) all RC bugs are fixed, the freeze is > to allow the existing bugs to be fixed whilst *protecting* the other > packages from breakage caused by new software being uploaded.
You can still fix bugs while new software is uploaded, and more generally RC bugs should be fixed ASAP. > The RC bug count only ever comes down once a freeze is in place. Developers should not wait for the freeze to fix RC bugs. > New software causes new bugs, that's inescapable. But new software also causes existing bugs to be fixed. The number of bugs tend to decrease, in particular in bug-fix releases (note that such releases are also blocked by the freeze). > To reduce the bug count, existing software must be fixed without > allowing new software to continue breaking things and whilst making > the absolute minimal changes to the software which is still working. > *That* is the freeze. No, buggy new software that breaks things should not enter testing in the first place. That's what unstable/testing is for. New buggy packages should remain in unstable while new versions of good packages could still enter testing for the next release. -- Vincent Lefèvre <vinc...@vinc17.net> - Web: <http://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <http://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon) -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130402145212.gf31...@xvii.vinc17.org
