cassandra-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Maciek Sakrejda <>
Subject Versioning policy?
Date Mon, 11 Jan 2016 03:29:41 GMT
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.


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message