[VOTE] Release Apache Cassandra 2.1.0-rc6
I propose the following artifacts for release as 2.1.0-rc6. As it is "just a RC", we'll keep the vote to a short 24h. sha1: 397c0b7c099cc1790c865d9dac7bd46b6194eddf Git: http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.1.0-rc6-tentative Artifacts: https://repository.apache.org/content/repositories/orgapachecassandra-1025/org/apache/cassandra/apache-cassandra/2.1.0-rc6/ Staging repository: https://repository.apache.org/content/repositories/orgapachecassandra-1025/ The artifacts as well as the debian package are also available here: http://people.apache.org/~slebresne/ The vote will be open for 24 hours (longer if needed). [1]: http://goo.gl/VUS8bD (CHANGES.txt) [2]: http://goo.gl/cA3LMH (NEWS.txt)
Re: [VOTE] Release Apache Cassandra 2.1.0-rc6
+1 On Aug 13, 2014 7:33 AM, "Sylvain Lebresne" wrote: > I propose the following artifacts for release as 2.1.0-rc6. As it is "just > a > RC", we'll keep the vote to a short 24h. > > sha1: 397c0b7c099cc1790c865d9dac7bd46b6194eddf > Git: > > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.1.0-rc6-tentative > Artifacts: > > https://repository.apache.org/content/repositories/orgapachecassandra-1025/org/apache/cassandra/apache-cassandra/2.1.0-rc6/ > Staging repository: > https://repository.apache.org/content/repositories/orgapachecassandra-1025/ > > The artifacts as well as the debian package are also available here: > http://people.apache.org/~slebresne/ > > The vote will be open for 24 hours (longer if needed). > > [1]: http://goo.gl/VUS8bD (CHANGES.txt) > [2]: http://goo.gl/cA3LMH (NEWS.txt) >
Re: [VOTE] Release Apache Cassandra 2.1.0-rc6
+1 On Wed, Aug 13, 2014 at 7:32 AM, Sylvain Lebresne wrote: > I propose the following artifacts for release as 2.1.0-rc6. As it is "just > a > RC", we'll keep the vote to a short 24h. > > sha1: 397c0b7c099cc1790c865d9dac7bd46b6194eddf > Git: > > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.1.0-rc6-tentative > Artifacts: > > https://repository.apache.org/content/repositories/orgapachecassandra-1025/org/apache/cassandra/apache-cassandra/2.1.0-rc6/ > Staging repository: > https://repository.apache.org/content/repositories/orgapachecassandra-1025/ > > The artifacts as well as the debian package are also available here: > http://people.apache.org/~slebresne/ > > The vote will be open for 24 hours (longer if needed). > > [1]: http://goo.gl/VUS8bD (CHANGES.txt) > [2]: http://goo.gl/cA3LMH (NEWS.txt) >
Re: [VOTE] Release Apache Cassandra 2.1.0-rc6
+1 On Aug 13, 2014 7:33 AM, "Sylvain Lebresne" wrote: > I propose the following artifacts for release as 2.1.0-rc6. As it is "just > a > RC", we'll keep the vote to a short 24h. > > sha1: 397c0b7c099cc1790c865d9dac7bd46b6194eddf > Git: > > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.1.0-rc6-tentative > Artifacts: > > https://repository.apache.org/content/repositories/orgapachecassandra-1025/org/apache/cassandra/apache-cassandra/2.1.0-rc6/ > Staging repository: > https://repository.apache.org/content/repositories/orgapachecassandra-1025/ > > The artifacts as well as the debian package are also available here: > http://people.apache.org/~slebresne/ > > The vote will be open for 24 hours (longer if needed). > > [1]: http://goo.gl/VUS8bD (CHANGES.txt) > [2]: http://goo.gl/cA3LMH (NEWS.txt) >
Summit Tickets for Cassandra Committers
If you are an Apache Cassandra Committer (have write access to the Cassandra git repository) and you plan to attend the summit, but don’t have tickets yet, please email me ASAP. We’ll make necessary arrangements. Thanks. P.S. Time is running out, so please try to email me by the end of the week.
Re: [VOTE] Release Apache Cassandra 2.1.0-rc6
I'd prefer to patch CASSANDRA-7743 first. On Wed, Aug 13, 2014 at 10:47 PM, Brandon Williams wrote: > +1 > On Aug 13, 2014 7:33 AM, "Sylvain Lebresne" wrote: > > > I propose the following artifacts for release as 2.1.0-rc6. As it is > "just > > a > > RC", we'll keep the vote to a short 24h. > > > > sha1: 397c0b7c099cc1790c865d9dac7bd46b6194eddf > > Git: > > > > > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.1.0-rc6-tentative > > Artifacts: > > > > > https://repository.apache.org/content/repositories/orgapachecassandra-1025/org/apache/cassandra/apache-cassandra/2.1.0-rc6/ > > Staging repository: > > > https://repository.apache.org/content/repositories/orgapachecassandra-1025/ > > > > The artifacts as well as the debian package are also available here: > > http://people.apache.org/~slebresne/ > > > > The vote will be open for 24 hours (longer if needed). > > > > [1]: http://goo.gl/VUS8bD (CHANGES.txt) > > [2]: http://goo.gl/cA3LMH (NEWS.txt) > > >
Re: [VOTE CLOSED] Release Apache Cassandra 2.0.10
Everything should be good now. Thanks! > On Aug 11, 2014, at 9:34 AM, Sylvain Lebresne wrote: > > Ok, ok, closing this vote for now. We'll re-roll as soon as the pig stuff > are fixed. > > > On Fri, Aug 8, 2014 at 10:07 PM, Jeremiah D Jordan > wrote: > >> I'm -1 on this until we get CqlRecordReader fixed (which will also fix the >> newly added in 2.0.10 Pig CqlNativeStoarge): >> https://issues.apache.org/jira/browse/CASSANDRA-7725 >> https://issues.apache.org/jira/browse/CASSANDRA-7726 >> >> Without those two things anyone using CqlStorage previously (which removed >> with the removal of CPRR) who updates to using CqlNativeStoarge will have >> broken scripts unless they are very very careful. >> >> >> -Jeremiah >> >>> On Aug 8, 2014, at 5:03 AM, Sylvain Lebresne wrote: >>> >>> I propose the following artifacts for release as 2.0.10. >>> >>> sha1: cd37d07baf5394d9bac6763de4556249e9837bb0 >>> Git: >> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.0.10-tentative >>> Artifacts: >> https://repository.apache.org/content/repositories/orgapachecassandra-1023/org/apache/cassandra/apache-cassandra/2.0.10/ >>> Staging repository: >> https://repository.apache.org/content/repositories/orgapachecassandra-1023/ >>> >>> The artifacts as well as the debian package are also available here: >>> http://people.apache.org/~slebresne/ >>> >>> The vote will be open for 72 hours (longer if needed). >>> >>> [1]: http://goo.gl/xzb9ky (CHANGES.txt) >>> [2]: http://goo.gl/nBI37B (NEWS.txt) >> >>
RFC try for s/ant/gradle/
Hi, Since there were some IRC posts regarding "realclean" when dependencies change, I thought about replacing ant with something else. It's not just because of that particular realclean but also on dependencies that don't get actually updated or even out-of-date IDE project files (.classpath) causing problems. This "something better" should have proper dependency management, doesn't require us to have dependency jars in git and be supported my major IDEs (IDEA / Eclipse). (Someone using Eclipse?). But such a change should not result in a folder or code refactoring game... Maven could be an option - but it has some drawbacks regarding the current folder structure. Maven can basically only emit one artifact per pom properly (plus some other files like -javadoc.jar or -sources.jar). So it might be required to change the folder structure (don't want that - merging would become a nightmare, if possible at all...). Grade would be a nice option. It is more a scripting language than a "static" construct like Maven's pom.xml. It is very flexible and seems to have all required features. Gradle has native support for Maven repositories. Gradle does not require the user to install Gradle (you can, but do not need to) - it comes with a small "wrapper" that fetches a Gradle binary. I've identified these "non-standard" blocks in build.xml: gen-cli-grammar: basically just a conditional exec gen-cql3-grammar: basically just a conditional exec generate-cql-html: basically just an exec write-java-license-headers / rat: basically just an exec emitting multiple jars (cassandra.jar, cassandra-thrift.jar, cassandra-clientutil.jar) from the same folder (build/classes/main+thrift): difficult with Maven gen-thrift-py: basically just an exec several test targets: is possible with Maven, but let's the pom.xml "explode" and is not easy to read By using Gradle I hope to get rid of dependency problems "realclean" dependency differences between build.xml and IDE since .project/.classpath not updated .project/.classpath cannot be generated because compilation fails due to dependency changes make the build file smaller remove binaries (dependencies) from git proper IDE support for IDEA + Eclipse? If Gradle works, it could be introduced like that: Keep both build.xml and Gradle build file up to date After a while change build.xml to act basically just as a "wrapper" for Gradle. Just to not "disturb" existing processes (Jenkins/CI) and give users a chance to recognize the change. Remove build.xml after some time Would be great to get some feedback what you think about this. Robert signature.asc Description: Message signed with OpenPGP using GPGMail
Re: RFC try for s/ant/gradle/
On Wed, Aug 13, 2014 at 2:59 PM, Robert Stupp wrote: > >- remove binaries (dependencies) from git > > Don't do that, the reason we have those in git is they don't get automatically upgraded.
Re: RFC try for s/ant/gradle/
Also, we have to publish license information on anything we ship in the binary jar. See CASSANDRA-802 and CASSANDRA-850 for the history here. On Wed, Aug 13, 2014 at 3:08 PM, Brandon Williams wrote: > On Wed, Aug 13, 2014 at 2:59 PM, Robert Stupp wrote: > >> >>- remove binaries (dependencies) from git >> >> > Don't do that, the reason we have those in git is they don't get > automatically upgraded. -- Jonathan Ellis Project Chair, Apache Cassandra co-founder, http://www.datastax.com @spyced
