On 6/18/06, Anthony Baxter <anthony at interlink.com.au> 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? > > Anyway, thought I'd open this up for discussion... 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. -Brett -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.python.org/pipermail/python-dev/attachments/20060618/4591757a/attachment.htm
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