Some packages have new releases more than once a month and sometimes it's
reasonable
to not skip stabilization of any version. Given version of a package is usually
no
longer tested by users after release of a newer version, so I suggest the
following
change to the policy of stabilizations:
On Sun, 2009-11-01 at 17:36 +0100, Arfrever Frehtes Taifersar Arahesis
wrote:
Some packages have new releases more than once a month and sometimes it's
reasonable
to not skip stabilization of any version. Given version of a package is
usually no
longer tested by users after release of a
Mart Raudsepp wrote:
Is it stated in any documentation that 30 days is a policy?
Not that I'm aware of - it is a guideline as you indicate. However,
don't expect anybody to actually take action on a STABLEREQ if there
isn't some kind of rationale for going stable so quickly.
The whole
Richard Freeman wrote:
Mart Raudsepp wrote:
Is it stated in any documentation that 30 days is a policy?
Not that I'm aware of - it is a guideline as you indicate. However,
don't expect anybody to actually take action on a STABLEREQ if there
isn't some kind of rationale for going stable
