Re: [VOTE] Release Apache Cassandra 3.2
+1 On Sat, Jan 9, 2016 at 12:32 PM, Robert Stupp wrote: > +1 > > -- > Robert Stupp > @snazy > > > > -- > Robert Stupp > @snazy > > Am 08.01.2016 um 22:12 schrieb Jake Luciani : > > > > I propose the following artifacts for release as 3.2. > > > > sha1: 3c6dfa4aa0b9ffb0a48a02b949bff2a8406764e6 > > Git: > > > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.2-tentative > > Artifacts: > > > https://repository.apache.org/content/repositories/orgapachecassandra-1096/org/apache/cassandra/apache-cassandra/3.2/ > > Staging repository: > > > https://repository.apache.org/content/repositories/orgapachecassandra-1096/ > > > > 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/T8geYN (CHANGES.txt) > > [2]: http://goo.gl/VDwYyf (NEWS.txt) >
Re: [VOTE] Release Apache Cassandra 3.2
+1 On Sunday, January 10, 2016, Sylvain Lebresne wrote: > +1 > > On Sat, Jan 9, 2016 at 12:32 PM, Robert Stupp > wrote: > > > +1 > > > > -- > > Robert Stupp > > @snazy > > > > > > > > -- > > Robert Stupp > > @snazy > > > Am 08.01.2016 um 22:12 schrieb Jake Luciani >: > > > > > > I propose the following artifacts for release as 3.2. > > > > > > sha1: 3c6dfa4aa0b9ffb0a48a02b949bff2a8406764e6 > > > Git: > > > > > > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.2-tentative > > > Artifacts: > > > > > > https://repository.apache.org/content/repositories/orgapachecassandra-1096/org/apache/cassandra/apache-cassandra/3.2/ > > > Staging repository: > > > > > > https://repository.apache.org/content/repositories/orgapachecassandra-1096/ > > > > > > 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/T8geYN (CHANGES.txt) > > > [2]: http://goo.gl/VDwYyf (NEWS.txt) > > >
Versioning policy?
There was a discussion recently about changing the Cassandra EOL policy on the users list [1], but it didn't really go anywhere. I wanted to ask here instead to clear up the status quo first. What's the current versioning policy? The tick-tock versioning blog post [2] states in passing that two major releases are maintained, but I have not found this as an official policy stated anywhere. For comparison, the Postgres project lays this out very clearly [3]. To be clear, I'm not looking for any official support, I'm just asking for clarification regarding the maintenance policy: if a critical bug or security vulnerability is found in version X.Y.Z, when can I expect it to be fixed in a bugfix patch to that major version, and when do I need to upgrade to the next major version. [1]: http://www.mail-archive.com/user@cassandra.apache.org/msg45324.html [2]: http://www.planetcassandra.org/blog/cassandra-2-2-3-0-and-beyond/ [3]: http://www.postgresql.org/support/versioning/
