Now the vote has passed, and I’ve merged from the release branch back to master, master branch is now open for commits.
The official announcement will happen tomorrow, after the artifacts have had chance to propagate to the mirrors. Julian > On Mar 17, 2016, at 5:30 PM, Julian Hyde <[email protected]> wrote: > > I started the vote for RC0. Because it’s a weekend I made the vote a bit > longer than the customary 72 hours — it ends at 12 noon (Pacific) on Monday. > Please vote! > > Maryann, If you find out more about the memory leak, please let us know. > > Issues 1114, 1148 and 1054 didn’t make it into the release. > > Michael sent me some corrections to the release notes but I forgot to include > them. They’ll go in before I publish the release. > > Julian > > >> On Mar 17, 2016, at 10:45 AM, Josh Elser <[email protected]> wrote: >> >> Wonderful, thanks! >> >> Julian Hyde wrote: >>> I see that the avatica-1.7.1 vote passed. Now we can proceed with >>> calcite-1.7.0. >>> >>> Josh, >>> >>> I’ll take care of merging the avatica-1.7.1 stuff back to master branch, >>> including the release notes and release announcement. And I’ll publish the >>> site. >>> >>> Then I have a few calcite patches to apply in master, then I hope to have >>> an RC0 for calcite-1.7.0 this afternoon. >>> >>>> On Mar 17, 2016, at 1:10 AM, Jesus Camacho >>>> Rodriguez<[email protected]> wrote: >>>> >>>> CALCITE-1158 could go in too: it is simple change to make >>>> AggregateRemoveRule extensible, it should not destabilize the release. >>> >>> Great, I’ll include it. >>> >>> Julian >>> >
