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 >

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

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 maj