Jeroen Roovers wrote:
>      Dear ebuild maintainers,
> 
> 
> thirty days is the norm for the minimal period between an ebuilds last
> non-keywording change while in the tree and the usual call for
> stabilisation. If you cannot find a pressing reason to push
> stabilisation forward, then don't ask. In the last few days I have seen
> several early calls for stabilisation (bugs #217148, #217845, #217841
> and #217839 for instance) where no adequate reason was given, in my
> opinion.

Given that 3 of the 4 are from one person, I wouldn't draw broad 
conclusion from this.

> A good reason might be an important fix of a severe bug, a fix for a
> build problem that couldn't be applied to a stable version but had to
> go into an ebuild revision, or a version/revision that fixes a security
> problem.
> 
> On the other hand, maybe these early stabilisation bug reports are a
> sign of the times and we need to shorten the normal thirty day period,
> become even more of a cutting edge distro - or at least discuss the
> options.

I'd say leave the current norm and smack the misbehaving maintainers :)

Caster
-- 
gentoo-dev@g.o mailing list