A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2009-May/089603.html below:

[Python-Dev] Shorter release schedule?

[Python-Dev] Shorter release schedule? [Python-Dev] Shorter release schedule?MRAB google at mrabarnett.plus.com
Wed May 13 00:25:26 CEST 2009
Antoine Pitrou 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.
> 
> If I'm wildly off-base, you can either flame me, ignore me, or assign me
> annoying release blockers involving memoryviews and weird character encodings :-)
> 
Next you'll be saying that they should be named after years. Python
2010, anyone? :-)

I think that releases should depend on whether there are enough changes
for one.
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4