On Tue, Mar 2, 2010 at 9:41 AM, William Hubbs <willi...@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-...@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
