Re: Versioning policy?

riate [3] http://cassandra.apache.org/download/ On Sun, Jan 10, 2016 at 9:29 PM, Maciek Sakrejda <mac...@heroku.com> wrote: > 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

Re: Versioning policy?

where. 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, t

Re: Versioning policy?

t; On Sun, Jan 10, 2016 at 9:29 PM, Maciek Sakrejda <mac...@heroku.com> wrote: >> >> 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 statu

Re: Versioning policy?

t; [2] 4.0 will be an ordinary tick-tock release after 3.11, but we will be > sunsetting deprecated features like Thrift so bumping the major version > seems appropriate > [3] http://cassandra.apache.org/download/ > >> On Sun, Jan 10, 2016 at 9:29 PM, Maciek Sakrejda <mac..

Re: Versioning policy?

odes; we'd like to have a better idea of what to expect with respect to > > patching and upgrading. A clear versioning policy like the one laid out > by > > Postgres would be very helpful. > > ​ > > >

Re: Versioning policy?

sers 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 off

Re: Versioning policy?

akrejda <mac...@heroku.com> wrote: > 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

Re: Versioning policy?

On Thu, Jan 14, 2016 at 4:26 PM, Jack Krupansky wrote: > Jonathan, just to complete the list, it would be help to state: > > 3.1.x will be maintained until > 3.2 will be maintained until > One of the confusing things about tick tock is that we're stuck with numbers

Re: Versioning policy?

t we will be > sunsetting deprecated features like Thrift so bumping the major version > seems appropriate > [3] http://cassandra.apache.org/download/ > > On Sun, Jan 10, 2016 at 9:29 PM, Maciek Sakrejda <mac...@heroku.com> > wrote: > > > There was a discussion recently about

Re: Versioning policy?

Thanks, Jonathan. The end-of-life (EOL) question is still dangling out there - when does 3.x go off support, after 3.x+3 or six months after 4.0? Or... six months after 5.0? -- Jack Krupansky On Thu, Jan 14, 2016 at 6:15 PM, Jonathan Ellis wrote: > On Thu, Jan 14, 2016 at

Re: Versioning policy?

re? We're getting ready to run a decent number of > nodes; we'd like to have a better idea of what to expect with respect to > patching and upgrading. A clear versioning policy like the one laid out by > Postgres would be very helpful. > ​ >

Re: Versioning policy?

Can anyone chime in here? We're getting ready to run a decent number of nodes; we'd like to have a better idea of what to expect with respect to patching and upgrading. A clear versioning policy like the one laid out by Postgres would be very helpful. ​