In linux.debian.devel, you wrote:
>
>I hope to fix this in the long run by having more frequent releases,
>so that maintainers are less anxious to get their packages in the
>upcoming release. In the short term... let's just hope :-)
>
How about creating woody at the freeze announcement instead
Adam Di Carlo wrote:
> * Release Critical Bugs
>
> With respect to fixing release critical bugs, I think there are two
> components to lowering this as a big problem. The first, as pointed
> out, is to *not* try to cram heavily broken things into unstable just
> prior to freeze, and it just requ
On Sun, May 09, 1999 at 03:43:58PM -0400, Adam Di Carlo wrote:
> Looking back at the slink freeze, I think we had two big problems
> which slowed us down by about a month: new X Window System packages,
> heavily broken, and the libc problems. I don't wish to cast any blame
> on the package manager
My take on the situation is that there are two reasons for why the
freeze takes a long time. The first is just fixing the release
critical bugs -- this commonly receives a lot of attention from this
list. The second is coordination between all the elements which are
required for release (boot-fl
4 matches
Mail list logo
