Gentoo Archives: gentoo-dev

From: "Olivier CrĂȘte" <tester@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] Policy for late/slow stabilizations
Date: Sun, 27 Jun 2010 15:48:10
In Reply to: [gentoo-dev] Policy for late/slow stabilizations by Markos Chandras
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. -- Olivier CrĂȘte tester@g.o Gentoo Developer


File name MIME type
signature.asc application/pgp-signature


Subject Author
Re: [gentoo-dev] Policy for late/slow stabilizations Jeroen Roovers <jer@g.o>
Re: [gentoo-dev] Policy for late/slow stabilizations Samuli Suominen <ssuominen@g.o>
Re: [gentoo-dev] Policy for late/slow stabilizations Markos Chandras <hwoarang@g.o>