I'm +1 on doing an 0.9.0 release, but would also like to suggest that we put together a list of 0.9.0 blockers before cutting the release branch. In the past we have frequently underestimated the amount of work required to get trunk into a releasable state, with the consequence that we up wasting time doing a lot of backports from trunk to the release branch. It would be great if we could avoid all of that this time around.
Thanks. Carl On Mon, Apr 2, 2012 at 6:33 PM, Ashutosh Chauhan <[email protected]>wrote: > Hi all, > > Branch for 0.8-r2 was created on Dec 7, almost four months ago. Between > then and now lots of cool stuff has landed in trunk waiting to be released > and get to users. I think its a good time now to get the ball rolling for > 0.9 release. If this sounds good, I would propose to cut a branch for 0.9 > later this week. Then we can focus on stabilizing the branch and subsequent > release from it. Thoughts? > > Thanks, > Ashutosh >
