Just curious -- is the lack of binary release intentional? I think other projects usually offer a "convenience" binary tgz.
On Thu, May 21, 2015 at 2:05 PM, Julian Hyde <[email protected]> wrote: > Hi all, > > I have created a build for Apache Calcite 1.3.0-incubating, release > candidate 1. > > Thanks to everyone who has contributed to this release. Mainly bug fixes > this > time, but this release adds support for modifiable views and filtered > aggregate > functions, and various improvements to the Avatica JDBC framework. You can > read the release notes here: > https://github.com/apache/incubator-calcite/blob/branch-1.3/doc/history.md > > The commit to be voted upon: > > http://git-wip-us.apache.org/repos/asf/incubator-calcite/commit/495f1859f84b41ae70b2099c3d15c696a49a5100 > > Its hash is 495f1859f84b41ae70b2099c3d15c696a49a5100. > > The artifacts to be voted on are located here: > > https://dist.apache.org/repos/dist/dev/incubator/calcite/apache-calcite-1.3.0-incubating-rc1 > > The hashes of the artifacts are as follows: > src.tar.gz.md5 1d084f05e11f202f69594152d1771d6d > src.tar.gz.sha1 e1189cd2de0c6096deac28b3d1a2c9be9bb88d6d > src.zip.md5 63ea0765b6c872454472e31ac18bc394 > src.zip.sha1 50f90a9f0b700a9617d63ca75687d8717dc4c434 > > A staged Maven repository is available for review at: > https://repository.apache.org/content/repositories/orgapachecalcite-1008 > > Release artifacts are signed with the following key: > https://people.apache.org/keys/committer/jhyde.asc > > Please vote on releasing this package as Apache Calcite 1.3.0-incubating. > > The vote is open for the next 120 hours (longer than usual, because of a > long weekend in the US, and closing at 15:00 Pacific on Tuesday) and passes > if a majority of > at least three +1 PPMC votes are cast. > > [ ] +1 Release this package as Apache Calcite 1.3.0-incubating > [ ] 0 I don't feel strongly about it, but I'm okay with the release > [ ] -1 Do not release this package because... > > > Here is my vote: > > +1 (binding) > > Julian >
