Re: [buildd] Etch?
On Fri, 4 Aug 2006, Geert Uytterhoeven wrote:
> On Fri, 4 Aug 2006, Finn Thain wrote:
> > On Fri, 4 Aug 2006, Geert Uytterhoeven wrote:
> > >
> > > Since most of the problems are caused by compiler issues, what
> > > guarantees that a
> > > release-without-packages-that-caused-obvious-problems doesn't
> > > contain non-obvious problems caused by those same compiler issues?
> > Was there ever a release with no bugs? No known bugs?
> Of course not.
> But an unreliable toolchain is a guarantee for more bugs.
I think I see what you meant: we might still meet the release criteria for
etch while there are still packages unbuilt due to toolchain bugs. Now
that _would_ be a problem for Gentoo ;-)
Anyway, I admire Wouter's ambition and high standards -- that's what makes
Debian what it is.
As I said earlier in the thread I don't see much difference between
releasing and not releasing... but I'm only an interested observer, and
I'm probably missing something. Assuming no toolchain problems, I'm
wondering what is real the benefit to releasing Etch on time?