How about if the maintainer wants wider testing, i.e. wants to move it out of package.mask and into ~arch but isn't confident it's ready yet for arch, adding a string variable to ebuilds indicating why the maintainer considers the package unstable, eg:
UNSTABLE="#100435, #100345, unconfirmed break with foo" The maintainer would simply alter this line as bugs get confirmed or resolved. If a package wants to stay ~arch for longer than normal, even though there are as yet no reports of problems, the maintainer can just keep it set to something: UNSTABLE="gaining maturity" The arch team could consider an ebuild without an UNSTABLE line as a candidate for stable, and it provides an easy way for maintainers to communicate what issues are known with a package to the arch team (and anyone else who is interested). The 30-day could be calculated from the $Header: of ebuilds that have no UNSTABLE, or where it's empty. Kev. -- gentoo-dev@gentoo.org mailing list
