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
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-dev@g.o
From: Samuli Suominen <ssuominen@g.o>
Subject: Re: Policy for late/slow stabilizations
Date: Sun, 27 Jun 2010 19:30:49 +0300
On 06/27/2010 06:47 PM, Olivier CrĂȘte wrote:
> On Sun, 2010-06-27 at 18:04 +0300, Markos Chandras wrote:
>> Moreover, slow arches introduce another problem as well. If a package is
>> marked stabled for their arch, but this package is quite old, and they fail to
>> stabilize a new version, we ( as maintainers ) can't drop the very old
>> ( and obsolete ) version of this package because we somehow will break
>> the stable tree for these arches. How should we act in this case?
>> Keep the old version around forever just to say that "hey, they do have
>> a stable version for our exotic arch".
> 
> I'd propose waiting a bit longer than 30 days.. Maybe 90 days, and then
> just drop the old ebuild. These arches will slowly lose stable keywords
> until their stable tree gets to a size that they can manage. And
> everyone will be winners. That said, when dropping the old keywords, you
> have to be careful to drop the stable keyword on all dependencies too so
> as to not drop break the tree for them.
> 

+1


References:
Policy for late/slow stabilizations
-- Markos Chandras
Re: Policy for late/slow stabilizations
-- Olivier CrĂȘte
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: Policy for late/slow stabilizations
Next by thread:
Re: Policy for late/slow stabilizations
Previous by date:
Re: Policy for late/slow stabilizations
Next by date:
Re: Policy for late/slow 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.