Erik Petrich <epetrich@...> åßðå:
> It's been over a year and 300+ changes since 2.4.0 was released.
> It would be good to do another "official/stable" release soon. The
> topic came up last fall, but seemed to fizzle out. To give us some
> deadlines to keep us focused this time, I'd like to propose the
> following schedule (subject to discussion & modification, of
> 20 March - 2 April (next two weeks): wrap up any major
> development in progress (preferably things that unlikely to
> cause new bugs)
2 weeks should be enough for major development merging. In addition,
since we haven't reached a final decision yet, we should allow at
least 1 week for this phase after we decide the final schedule.
> 3 April - 16 April: no commits other than bug fixes that are
> extremely unlikely to have unintended side effects.
I think this phase doesn't need to be 2 weeks. 1 week should be
enough (since it can be merged in phase 1). Perhaps we should give
more time for the next phases...
> 17 April: generate release candidates
> 17 April - 30 April: Test release candidates; only deal with
> major bugs
> 1 May: Hopefully, publicly issue 2.5.0 release
> Please reply so that we can reach a clear consensus soon
> preferably by the end of March).