Anthony Baxter <anthony at interlink.com.au> writes:
> 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...
I agree with you. If people want to work on new features, they can
create branches for that -- by default, bug fixes should go into 2.5
without further effort.
Cheers,
mwh
--
I wouldn't trust the Anglo-Saxons for much anything else. Given
they way English is spelled, who could trust them on _anything_ that
had to do with writing things down, anyway?
-- Erik Naggum, comp.lang.lisp
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