Re: [gentoo-user] How packages are made stable

[Steve Dibb <beandog@gentoo.org>]

Andrey Gerasimenko wrote:
> On Fri, 05 Jan 2007 11:49:30 +0300, Robert Cernansky 
> <hslists2@zoznam.sk> wrote:
> 
>> On Thu, 04 Jan 2007 13:49:48 -0700 Steve Dibb <beandog@gentoo.org> wrote:
>>
>>> Andrey Gerasimenko wrote:
>>> > Looking at the Portage tree, I see that some packages are kept ~x86
>>> > for long time without any bugs referenced in the changelog or
>>> > Bugzilla. How are they being made stable (or where in the docs is the
>>> > process described)?
>>> They need to be in the tree for at least 30 days, no bugs, and if
>>> someone files a stable request ebuild, then an arch tester will test it,
>>> and then a dev will keyword it stable.
>>>
>>> Most stuff doesnt get marked stable mostly because there aren't any
>>> stable requests.
>>
>> Stabilisation bug it not a requirement.

Actually, everything I said in that last email was a little off.  Stabilization 
bugs are required because ultimately it is the architecture team that is going 
to mark it stable, not the developer.  There are some cases where things can go 
directly stable (such as security vulnerabilities), but those are the exception 
and not the rule.

So if you want something stable, do all the checks, file a bug, and copy all the 
arches that it applies to.  You can see which ones use it on 
http://packages.gentoo.org/

Steve
-- 
gentoo-user@gentoo.org mailing list