Re: Release update: freeze progress, closing date for non-RC fixes

On Wed, May 18, 2005 at 07:17:46PM -0700, Steve Langasek wrote: > On Thu, May 19, 2005 at 12:55:12AM +0200, Adrian Bunk wrote: > > On Tue, May 17, 2005 at 04:42:35PM -0700, Steve Langasek wrote: > > >... > > > According to , the official > > > count of rele

Re: Release update: freeze progress, closing date for non-RC fixes

On Thu, May 19, 2005 at 12:55:12AM +0200, Adrian Bunk wrote: > On Tue, May 17, 2005 at 04:42:35PM -0700, Steve Langasek wrote: > >... > > According to , the official > > count of release-critical bugs affecting testing is 61. Since security > > bugs are an

Re: Release update: freeze progress, closing date for non-RC fixes

On Thu, May 19, 2005 at 01:49:06AM +0200, Bernd Eckenfels wrote: > In article <[EMAIL PROTECTED]> you wrote: > > - the exclusion of bugs that are tagged both "sarge" and "sid" > > (e.g. #303860) is obviously wrong > BTW: is there a way to make unstable updates not close the bugs in question > but

Re: Release update: freeze progress, closing date for non-RC fixes

In article <[EMAIL PROTECTED]> you wrote: > - the exclusion of bugs that are tagged both "sarge" and "sid" > (e.g. #303860) is obviously wrong BTW: is there a way to make unstable updates not close the bugs in question but mark them woody and/or sarge? If not, should the changelog simply contain

Re: Release update: freeze progress, closing date for non-RC fixes

On Tue, May 17, 2005 at 04:42:35PM -0700, Steve Langasek wrote: >... > According to , the official > count of release-critical bugs affecting testing is 61. Since security > bugs are an, er, "renewable resource", and can be fixed out-of-band, we > can excl