Back in June, Jonathan posted: "After 2.2.0 is released, 2.0 will reach end-of-life as planned. After 3.0.0 is released, 2.1 will also reach end of life. This is earlier than expected, but 2.2 will be very close to as stable as 2.1 and users will be well served by upgrading. We will maintain the 2.2 stability series until 4.0 is released, and 3.0 for six months after that."
I can't recall seeing any more formal articulation of EOL/EOSL for Cassandra in recent years, other than the DataStax DSE support policy: http://www.datastax.com/support-policy/supported-software http://www.datastax.com/support-policy For DataStax Cerified Cassandra releases there is this stated policy: "End of Life Support - Certified Cassandra customers receive full commercial software lifecycle support that includes both certified software updates and expert support for earlier versions of Certified Cassandra that they still have deployed in production." But that is a little vague and has no hard date or time intervals. I mean, it sounds as if the mere fact that you have it in production means DataStax will support it forever. See: http://www.datastax.com/products/datastax-enterprise-production-certified-cassandra Cassandra 2.0.17 is in DSE 4.6.x which has a stated EOL of June 2, 2016 and stated EOSL of December 2, 2016. Cassandra 2.1.11 (not 2.1.12) is in DSE 4.8.x (and 4.7) which has a stated EOL of March 23, 2017 and stated EOSL of September 23, 2017. If you really care about 2.1.12 vs. 2.1.11, DataStax tends to include additional bug fixes if they seem critical. That list is here: https://docs.datastax.com/en/datastax_enterprise/4.8/datastax_enterprise/RNcassChanges.html?scroll=RNcassFixes__483_unique_1 -- Jack Krupansky On Wed, Jan 6, 2016 at 12:41 PM, Anuj Wadehra <anujw_2...@yahoo.co.in> wrote: > Hi, > > Can someone help me by providing formal dates of EOL for Cassandra 2.0.17 > and 2.1.12? > > > Thanks > Anuj > > > > > Sent from Yahoo Mail on Android > <https://overview.mail.yahoo.com/mobile/?.src=Android> >
