[Python-Dev] Shorter release schedule?

[Collin Winter]

On Tue, May 12, 2009 at 3:06 PM, Antoine Pitrou <solipsis at pitrou.net> wrote:
> Hello,
>
> Just food for thought here, but seeing how 3.1 is going to be a real featureful
> schedule despite being released shortly after 3.0, wouldn't it make sense to
> tighten future release planning a little? I was thinking something like doing a
> major release every 12 months (rather than 18 to 24 months as has been
> heuristically the case lately). This could also imply switching to some kind of
> loosely time-based release system.

I'd be in favor of a shorter, 12-month release cycle. I think the
limiting resource would be the time and energy of the release managers
and the package builders for Windows, etc. Provided it's not a tax on
the release staff, I think shorter release cycles would be a benefit
to the community. My own experience with time-based releases at work
is that it greatly helps focus energy and attention, knowing that you
can't simply delay the release if you slack off on your features/bugs.

Collin