I think freeze on Wednesday (22nd) might be a bit ambitious. I suggest that we stabilize from Wednesday, post a snapshot, ask people to run their test suites on that snapshot, and start the first vote the following Monday (27th).
I am working on 751 and also 794 and would really like to get these into the release. I think I can finish by Wednesday. We should strongly consider fixing issues raised by incubator PMC members during the last release vote: 741, 743, 747. And I'd love it if we could get 687, 705, 783 into the release, but I wouldn't hold the release for them. Julian * https://issues.apache.org/jira/browse/CALCITE-687 Make RemoteDriverTest.testStatementLifecycle thread-safe * https://issues.apache.org/jira/browse/CALCITE-705 AvaticaStatement execute method to support DML * https://issues.apache.org/jira/browse/CALCITE-741 DEPENDENCIES should not be empty * https://issues.apache.org/jira/browse/CALCITE-743 Source distributions .tar.gz and .zip should contain identical files * https://issues.apache.org/jira/browse/CALCITE-747 Use standard format for .sha1 and .md5 files * https://issues.apache.org/jira/browse/CALCITE-751 Push aggregate with aggregate functions through join * https://issues.apache.org/jira/browse/CALCITE-783 Infer collation of Project using monotonicity * https://issues.apache.org/jira/browse/CALCITE-794 Detect cycles when computing statistics On Fri, Jul 17, 2015 at 12:04 PM, Aman Sinha <[email protected]> wrote: > +1 for doing the 1.4 release. I hope to get CALCITE-714 fixed by next > week and would like to include it in the release. > > Aman > > On Fri, Jul 17, 2015 at 11:42 AM, Jacques Nadeau <[email protected]> wrote: > >> I'm not hearing any other perspective on doing a release. Can we hear from >> other committers on their support for a 1.4 release? How do people feel >> about freeze Wednesday next week? >> >> thanks, >> Jacques >> >> On Wed, Jul 8, 2015 at 1:43 PM, Julian Hyde <[email protected]> wrote: >> >> > Thanks for volunteering! >> > >> > Here's the release procedure: >> > >> > >> https://calcite.incubator.apache.org/docs/howto.html#making-a-release-for-calcite-committers >> > (Only one person has ever followed it, and always on the same machine, >> > so there are bound to be improvements.) >> > >> > I also use this script to generate all of those pesky emails: >> > https://github.com/julianhyde/share/blob/master/tools/relMail.sh >> > >> > Let's agree on a timeline for the release. I thought the several-day >> > "stabilization period" before the first vote, during which people ran >> > their own tests, worked well last time, so I'd like to do that again. >> > >> > Julian >> > >> > On Wed, Jul 8, 2015 at 9:03 AM, Jacques Nadeau <[email protected]> >> wrote: >> > > +1 on a new release. >> > > >> > > Do you have the release procedure doc'd? I'm up for being the release >> > > manager (if no one else raises their hand) but want to make sure I >> follow >> > > the steps as you follow them since they are probably a little different >> > > than Drill. >> > > >> > > Jacques >> > > >> > > On Mon, Jul 6, 2015 at 10:42 PM, Julian Hyde <[email protected]> wrote: >> > > >> > >> Seems about time for Calcite release 1.4. Say, freeze in a week or >> two, >> > >> release a week or so later. Anyone have any time constraints? Any >> > >> volunteers to be release manager? >> > >> >> > >> Julian >> > >> >> > >> >> > >>
