> 2.1.8 release vote right on top of 2.1.6 and 2.1.7. I havent dug into the specific issues, but given the small list of changes and release velocity, those two older releases should probably be considered an "upgrade now" trigger with clients.
Thanks for the heads up. Guess we should keep a list of this sort of thing somewhere. A ----------------- Aaron Morton New Zealand @aaronmorton Co-Founder & Principal Consultant Apache Cassandra Consulting http://www.thelastpickle.com On Mon, Jul 6, 2015 at 12:52 PM, Gary Dusbabek <gdusba...@gmail.com> wrote: > +1 > > On Mon, Jul 6, 2015 at 12:04 PM, Jake Luciani <j...@apache.org> wrote: > > > I propose the following artifacts for release as 2.1.8. > > > > sha1: db39257c34152f6ccf8d53784cea580dbfe1edad > > Git: > > > > > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.1.8-tentative > > Artifacts: > > > > > https://repository.apache.org/content/repositories/orgapachecassandra-1063/org/apache/cassandra/apache-cassandra/2.1.8/ > > Staging repository: > > > https://repository.apache.org/content/repositories/orgapachecassandra-1063/ > > > > The artifacts as well as the debian package are also available here: > > http://people.apache.org/~jake > > > > The vote will be open for 72 hours (longer if needed). > > > > [1]: http://goo.gl/BFYiEO (CHANGES.txt) > > [2]: http://goo.gl/24XaPp (NEWS.txt) > > >
