Hi All, Please consider branch-1.2 frozen for now, till after the release process.
Thanks, -Sushanth On Tue, Jun 16, 2015 at 12:28 AM, Sushanth Sowmyan <[email protected]> wrote: > Hi folks, > > It's been nearly a month since 1.2.0, and when I did that release, I said > I'd keep the branch open for any further non-db-changing, non-breaking > patches, and from the sheer number of patches registered on the status page, > that's been a good idea. > > Now, I think it's time to start drawing that to a close to see an > stabilization update, and I would like to begin the process of rolling out > release candidates for 1.2.1. I would like to start rolling out an RC0 by > Wednesday night if no one objects. > > For now, the rules on committing to branch-1.2 remain the same: > a) commit to branch-1 & master first > b) add me as a watcher on that jira > c) add the bug to the release status wiki. > > Once I start the release process, I will once again increase the bar for > commits as we did the last time. That said, this time, once we finish the > release for 1.2.1, the bar on further commits to branch-1.2 is intended to > remain at a higher level, so as to make sure we don't have too much of a > back porting hassle - we will soon try to limit our commits to branch-1 and > master only. > > Cheers, > -Sushanth
