From: Lie Ryan <lie.1296@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Official document for stabilization policy/guideline
Date: Tue, 02 Mar 2010 02:39:47 +1100 [thread overview]
Message-ID: <hmgn55$cko$1@dough.gmane.org> (raw)
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?
next reply other threads:[~2010-03-01 15:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-01 15:39 Lie Ryan [this message]
2010-03-01 18:32 ` [gentoo-user] Official document for stabilization policy/guideline Alan McKinnon
2010-03-01 21:31 ` Justin
2010-03-02 8:30 ` Justin
2010-03-02 17:41 ` William Hubbs
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='hmgn55$cko$1@dough.gmane.org' \
--to=lie.1296@gmail.com \
--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