[gentoo-user] Official document for stabilization policy/guideline

[gentoo-user] Official document for stabilization policy/guideline

[Lie Ryan]

I've found a few people referencing to a "30-day stabilization policy"
which basically says a package must be at least 30-days-old to be
considered for stabilization, but is there any document that serves as
an official guideline/checklist on how to consider to stabilize a
package? Is the 30-day policy the only policy?

I've been running several ~arch-ed packages that appears to be compile
and runs fine on my machine and would like to vote them for
stabilization. Is it enough to just open a bug issue and pray that the
arch manager would notice?

Re: [gentoo-user] Official document for stabilization policy/guideline

[Alan McKinnon]

On Monday 01 March 2010 17:39:47 Lie Ryan wrote:
> I've found a few people referencing to a "30-day stabilization policy"
> which basically says a package must be at least 30-days-old to be
> considered for stabilization, but is there any document that serves as
> an official guideline/checklist on how to consider to stabilize a
> package? Is the 30-day policy the only policy?

30 days has always been the strong suggestion. Perhaps not always applied, but 
always there as far as I recall.


> 
> I've been running several ~arch-ed packages that appears to be compile
> and runs fine on my machine and would like to vote them for
> stabilization. Is it enough to just open a bug issue and pray that the
> arch manager would notice?

Yes, just open a new bug in b.g.o.

The bug wranglers will assign it to the appropriate team and you will get 
email notifications when something happens. This lets you check in on the bug 
every soon often to observe progress or perhaps bump if a long period of 
inactivity has passed.


-- 
alan dot mckinnon at gmail dot com

Re: [gentoo-user] Official document for stabilization policy/guideline

[Justin]

On 01/03/10 16:39, Lie Ryan wrote:
> I've found a few people referencing to a "30-day stabilization policy"
> which basically says a package must be at least 30-days-old to be
> considered for stabilization, but is there any document that serves as
> an official guideline/checklist on how to consider to stabilize a
> package? Is the 30-day policy the only policy?
> 
> I've been running several ~arch-ed packages that appears to be compile
> and runs fine on my machine and would like to vote them for
> stabilization. Is it enough to just open a bug issue and pray that the
> arch manager would notice?
> 
> 
The policy says "30 day bug free", but it is always appreciated to get
feedback from users about packages which are stable on their systems. So
please go ahead and file bugs. If the maintainer has any objections
against a stabilization, you will be informed about that in the bug.

justin

Re: [gentoo-user] Official document for stabilization policy/guideline

[Justin]

[-- Attachment #1: Type: text/plain, Size: 835 bytes --]

On 01/03/10 16:39, Lie Ryan wrote:
> I've found a few people referencing to a "30-day stabilization policy"
> which basically says a package must be at least 30-days-old to be
> considered for stabilization, but is there any document that serves as
> an official guideline/checklist on how to consider to stabilize a
> package? Is the 30-day policy the only policy?
> 
> I've been running several ~arch-ed packages that appears to be compile
> and runs fine on my machine and would like to vote them for
> stabilization. Is it enough to just open a bug issue and pray that the
> arch manager would notice?
> 
> 
You might be interested in those two things too


http://phajdan-jr.blogspot.com/2010/03/stabilizing-package-is-serious-thing.html

http://www.mail-archive.com/gentoo-dev@lists.gentoo.org/msg36433.html


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]

Re: [gentoo-user] Official document for stabilization policy/guideline

[William Hubbs]

[-- Attachment #1: Type: text/plain, Size: 1169 bytes --]

On Tue, Mar 02, 2010 at 09:30:18AM +0100, Justin wrote:
> On 01/03/10 16:39, Lie Ryan wrote:
> > I've found a few people referencing to a "30-day stabilization policy"
> > which basically says a package must be at least 30-days-old to be
> > considered for stabilization, but is there any document that serves as
> > an official guideline/checklist on how to consider to stabilize a
> > package? Is the 30-day policy the only policy?
> > 
> > I've been running several ~arch-ed packages that appears to be compile
> > and runs fine on my machine and would like to vote them for
> > stabilization. Is it enough to just open a bug issue and pray that the
> > arch manager would notice?
> > 
> > 
> You might be interested in those two things too
> 
> 
> http://phajdan-jr.blogspot.com/2010/03/stabilizing-package-is-serious-thing.html
> 
> http://www.mail-archive.com/gentoo-dev@lists.gentoo.org/msg36433.html
> 

In a nutshell, anyone can request stabilization of a package.  If
something has been in the tree for at least 30 days without issues and
there isn't a stabilization request filed for it already, feel free
to file one.

William


[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] Official document for stabilization policy/guideline

[Mark Loeser]

Lie Ryan <lie.1296@gmail.com> said:
> I've been running several ~arch-ed packages that appears to be compile
> and runs fine on my machine and would like to vote them for
> stabilization. Is it enough to just open a bug issue and pray that the
> arch manager would notice?

The general policy is here:

http://devmanual.gentoo.org/keywording/index.html#moving-from-~arch-to-arch

Open a bug and let the package maintainer decide if that version should
go stable yet, or not at all.  We don't mark every version of each
package stable since that would waste a lot of cycles all around.

-- 
Mark Loeser
email         -   halcy0n AT gentoo DOT org
email         -   mark AT halcy0n DOT com
web           -   http://www.halcy0n.com

Re: [gentoo-user] Official document for stabilization policy/guideline

[Mark Knecht]

On Tue, Mar 2, 2010 at 9:41 AM, William Hubbs <williamh@gentoo.org> wrote:
> On Tue, Mar 02, 2010 at 09:30:18AM +0100, Justin wrote:
>> On 01/03/10 16:39, Lie Ryan wrote:
>> > I've found a few people referencing to a "30-day stabilization policy"
>> > which basically says a package must be at least 30-days-old to be
>> > considered for stabilization, but is there any document that serves as
>> > an official guideline/checklist on how to consider to stabilize a
>> > package? Is the 30-day policy the only policy?
>> >
>> > I've been running several ~arch-ed packages that appears to be compile
>> > and runs fine on my machine and would like to vote them for
>> > stabilization. Is it enough to just open a bug issue and pray that the
>> > arch manager would notice?
>> >
>> >
>> You might be interested in those two things too
>>
>>
>> http://phajdan-jr.blogspot.com/2010/03/stabilizing-package-is-serious-thing.html
>>
>> http://www.mail-archive.com/gentoo-dev@lists.gentoo.org/msg36433.html
>>
>
> In a nutshell, anyone can request stabilization of a package.  If
> something has been in the tree for at least 30 days without issues and
> there isn't a stabilization request filed for it already, feel free
> to file one.
>
> William
>
>

In the __very__ old days wasn't there some measure of how many times
it's been downloaded? 30 days and 5 downloads vs 30 days and 5000
downloads really might be different in terms of stability.

Maybe there never was but it seemed like folks talked about back in
about 2000 or so...

- Mark

[gentoo-user] Re: Official document for stabilization policy/guideline

[Lie Ryan]

On 03/03/2010 04:52 AM, Mark Loeser wrote:
> Lie Ryan <lie.1296@gmail.com> said:
>> I've been running several ~arch-ed packages that appears to be compile
>> and runs fine on my machine and would like to vote them for
>> stabilization. Is it enough to just open a bug issue and pray that the
>> arch manager would notice?
> 
> The general policy is here:
> 
> http://devmanual.gentoo.org/keywording/index.html#moving-from-~arch-to-arch
> 
> Open a bug and let the package maintainer decide if that version should
> go stable yet, or not at all.  We don't mark every version of each
> package stable since that would waste a lot of cycles all around.
> 

Thanks, these are exactly what I've not been able to look for for some time.