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/2006-June/066231.html below:

[Python-Dev] When to branch release25-maint?

[Python-Dev] When to branch release25-maint? [Python-Dev] When to branch release25-maint?Raymond Hettinger rhettinger at ewtllc.com
Mon Jun 19 18:13:32 CEST 2006
Anthony Baxter wrote:

>A question has been asked about branching release25-maint at the time 
>of beta1. I was actually thinking about doing this for 2.5rc1 - once 
>we're in release candidate stage we want to really be careful about 
>checkins. I'm not sure it's worth branching at beta1 - it's a bit 
>more work all round, vs what I suspect will be a small amount of 2.6 
>work landing on the trunk nownownow. Also, I'd prefer people's cycles 
>be spent on bughunting 2.5 rather than worrying about shiny new 
>features for the release that's, what, 18 months away? 
>  
>
I recommend holding-off on a 2.6 branch until someone actually
has some non-trivial amount of 2.6 code ready for a commit.
My guess is that we are all focused on 2.5 or are participating
in intoxicating Py3k discussions.


Raymond

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