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