Gentoo Logo
Gentoo Spaceship

Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-dev
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
To: gentoo-dev@g.o
From: Richard Freeman <rich0@g.o>
Subject: Re: [RFC] Improve policy of stabilizations
Date: Sun, 01 Nov 2009 13:19:39 -0500
Mart Raudsepp wrote:
> Is it stated in any documentation that 30 days is a policy?

Not that I'm aware of - it is a guideline as you indicate.  However, 
don't expect anybody to actually take action on a STABLEREQ if there 
isn't some kind of rationale for going stable so quickly.

The whole point of stable is that they provide some sanity to the 
release process - if upstream releases a new version every other week 
then perhaps we should either:

1.  Question whether it should go stable at all.
2.  Pick a version once in a while and target it for stabilization, 
backporting fixes as needed.

We don't need to be Debian stable, but if the only reason for 
stabilizing a package is that upstream has already moved on, then I 
think we're making a mistake.  In fact, if upstream abandoned a release 
after only two weeks that would be a good reason NOT to stabilize it.

End users can always run ~arch if they need to - at least this way they 
know in advance what they're getting into.

Re: [RFC] Improve policy of stabilizations
-- Petteri R├Ąty
[RFC] Improve policy of stabilizations
-- Arfrever Frehtes Taifersar Arahesis
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
[RFC] Improve policy of stabilizations
Next by thread:
Re: [RFC] Improve policy of stabilizations
Previous by date:
Lastrite: gnome-extra/gnome-keyring-manager
Next by date:
Re: [RFC] Improve policy of stabilizations

Updated Jun 29, 2012

Summary: Archive of the gentoo-dev mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.