David Anderson wrote:
> Following the thread on dev@ and the thread on users@ asking our users
> what we should do with 1.5, I propose we branch the 1.5.x release
> branch at the end of this month.
> - A few people remarked that getting the features we have now "out
> there" is also good for merge tracking stabilization, as we will have
> time to address bugs in these features before we release the merge
> tracking behemoth, and could therefore focus more on merge tracking
> for 1.6.
> Personally speaking, I like the stabilization argument (MT is a big
> enough code change as it is, let's try to get other code changes out
> of the way), as well as catering to those who need stuff other than
> merge tracking as soon as possible.
Strong +1 to branching 1.5.x in 2 weeks.
The presence of Cyrus SASL support alone justifies the release from a
feature POV, IMO, and the arguments regarding stabilization, quoted
above, feel very very right to me.
I do not believe inserting an extra release cycle will slow down MT
development - even if all of the committers who have been working on MT,
remain focussed on MT, I think there's enough others of us to work on
the release engineering.
Received on Sun Mar 18 17:20:27 2007