From: William Hubbs <williamh@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Official document for stabilization policy/guideline
Date: Tue, 2 Mar 2010 11:41:50 -0600 [thread overview]
Message-ID: <20100302174150.GA26914@linux1> (raw)
In-Reply-To: <4B8CCC9A.6040502@j-schmitz.net>
[-- 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 --]
next prev parent reply other threads:[~2010-03-02 17:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-01 15:39 [gentoo-user] Official document for stabilization policy/guideline Lie Ryan
2010-03-01 18:32 ` Alan McKinnon
2010-03-01 21:31 ` Justin
2010-03-02 8:30 ` Justin
2010-03-02 17:41 ` William Hubbs [this message]
2010-03-02 18:03 ` Mark Knecht
2010-03-02 17:52 ` Mark Loeser
2010-03-02 19:04 ` [gentoo-user] " Lie Ryan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100302174150.GA26914@linux1 \
--to=williamh@gentoo.org \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox