Considering that 2.1.6 was just released and it is the first “stable” release ready for production in the 2.1 series, won’t it be too soon to EOL 2.1.x when 3.0 comes out in September?
Mohammed From: Jonathan Ellis [mailto:jbel...@gmail.com] Sent: Thursday, June 11, 2015 10:14 AM To: user Subject: Re: Cassandra 2.2, 3.0, and beyond As soon as 8099 is done. On Thu, Jun 11, 2015 at 11:53 AM, Pierre Devops <pierredev...@gmail.com<mailto:pierredev...@gmail.com>> wrote: Hi, 3.x beta release date ? 2015-06-11 16:21 GMT+02:00 Jonathan Ellis <jbel...@gmail.com<mailto:jbel...@gmail.com>>: 3.1 is EOL as soon as 3.3 (the next bug fix release) comes out. On Thu, Jun 11, 2015 at 4:10 AM, Stefan Podkowinski <stefan.podkowin...@1und1.de<mailto:stefan.podkowin...@1und1.de>> wrote: > We are also extending our backwards compatibility policy to cover all 3.x > releases: you will be able to upgrade seamlessly from 3.1 to 3.7, for > instance, including cross-version repair. What will be the EOL policy for releases after 3.0? Given your example, will 3.1 still see bugfixes at this point when I decide to upgrade to 3.7? -- Jonathan Ellis Project Chair, Apache Cassandra co-founder, http://www.datastax.com @spyced -- Jonathan Ellis Project Chair, Apache Cassandra co-founder, http://www.datastax.com @spyced
