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
