On Tue, Sep 14, 1999 at 09:09:36AM +0300, Antti-Juhani Kaijanaho wrote: > On Mon, Sep 13, 1999 at 05:54:00PM -0400, Michael Stone wrote: > > What is your accepted rate of bug closings? > > One that makes the bug count decrease, or at least constant. Can you force that ratio? Can you force people to change the rate at which bugs are introduced or closed? No. You can't force volunteers to do anything. That's the reality of the situation. Reiterating what you would like to see is not going to help find a real solution for dealing with a release. > > packages listed above, none of the other so-called Release Critical Bugs > > is really release critical > > The definition of release critical bug is the following: "fix the bug or > risk either removal of the package from the distribution, or postponing > of the release". Why should the presence of bugs in non-critical packages affect the freeze date or raise the possibility of postponing the release? I'm not interested in a requoting of the historic definition because I am questioning the utility of that definition. Justify your statement. Mike Stone
Attachment:
pgp50WCDbJPqW.pgp
Description: PGP signature