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? > > The policy says "30 day bug free", but it is always appreciated to get feedback from users about packages which are stable on their systems. So please go ahead and file bugs. If the maintainer has any objections against a stabilization, you will be informed about that in the bug.
justin
