I didn't do an immediate -1 because I wanted to have a discussion. Not waiting for the discussion to complete before calling the vote was unfortunate.
What was the big exception to spinning another release? To me, an Apache release's two most important criteria are correct licensing and a default build that works. On Apr 10, 2015 10:14 AM, "Julian Hyde" <[email protected]> wrote: > I'd rather press ahead with the release. This is a minor issue in new > functionality, and shows up in the test suite (not the build per se). > I've logged https://issues.apache.org/jira/browse/CALCITE-677 and will > mention it in the release notes. > > On Fri, Apr 10, 2015 at 8:34 AM, Jacques Nadeau <[email protected]> > wrote: > > Build fails seems like a showstopper to me, especially if the fix is one > > liner. Would rather redo here than have the Incubator general shoot it > > down. > > On Apr 10, 2015 2:13 AM, "Vladimir Sitnikov" < > [email protected]> > > wrote: > > > >> I've added @Ignore to the particular test and it went through. > >> It's a bit annoying to break "mvn install", however I would not > >> consider that a show-stopper either. > >> > >> Build works, mat-calcite-plugin works with Calcite 1.2.0-incubating. > >> > >> I would consider several modifications to mvn poms (see [1]), however > >> those do not block the release either. > >> > >> +1 for the release > >> > >> [1]: > >> > https://issues.apache.org/jira/browse/CALCITE-619?focusedCommentId=14489188&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14489188 > >> > >> Vladimir > >> >
