List Archive: gentoo-releng
Note: Due to technical difficulties, the Archives are currently not up to date.
provides an alternative service for most mailing lists.c.f. bug 424647
> > we'd never release ~arch tarballs
> I'm talking testing, you're thinking stable...
> Testers by definition do not want old stuff. The reason they are
> testing is they want new stuff. Yes, they understand the risk. In
> Debian they use "unstable" and "experimental" branches.
We have to think of people that install the first time or rely on
having a stable system, they need arch as it is tested. A fixed and
tested status has the pro of having less problems for Newbies.
> > I think your idea of how Gentoo releases work is a bit skewed.
> > Everything comes from stable. Always.
> I'm not clear how I said otherwise? Well, okay, straighten me out ...
> My understanding is
> * Gentoo has two parallel ongoing branches, arch and ~arch
> * ~arch has more recent packages than arch but less stability
> * both branches keep upgrading over time with bug/security/feature
Correct. This is done by teams per architecture, have a look at
> * the only stage3 tarballs that exist are for the previous mega public
> * Gentoo releng team plants a pole in the ground and ~arch becomes
> arch "beta"
No. There is a snapshot taken which contains the packages stable at
the moment of shooting.
> * arch "beta" quickly turns into arch-stable, while a new ~arch forks
We don't have an immediate switch, the parts of the tree move
constantly and at different speeds.
> Rolling tarballs for both arch and ~arch together is no more work than
> one or the other. It would be the same automated stuff.
Problems that occur one day might blow support...so those automated
stages need to be unsupported and we would win nothing out of it.
Christian Faulhammer, Gentoo Lisp project
<URL:http://www.gentoo.org/proj/en/lisp/>, #gentoo-lisp on FreeNode