Showing content from http://mail.python.org/pipermail/python-dev/attachments/20060618/4591757a/attachment.htm below:
On 6/18/06, <b class="gmail_sendername">Anthony Baxter</b> <<a href="mailto:anthony@interlink.com.au">anthony@interlink.com.au</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
A question has been asked about branching release25-maint at the time<br>of beta1. I was actually thinking about doing this for 2.5rc1 - once<br>we're in release candidate stage we want to really be careful about<br>checkins. I'm not sure it's worth branching at beta1 - it's a bit
<br>more work all round, vs what I suspect will be a small amount of 2.6<br>work landing on the trunk nownownow. Also, I'd prefer people's cycles<br>be spent on bughunting 2.5 rather than worrying about shiny new<br>features for the release that's, what, 18 months away?
<br><br>Anyway, thought I'd open this up for discussion...</blockquote><div><br>Sounds reasonable to me. Betas could still have more semantic changes for bug fixes than a release candidate might allow and thus make the branch too early a step at b1.
<br><br>-Brett<br></div><br></div>
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