HAPPY to see that Apache Cassandra web site has been updated to include EOL
information :) Thanks !!!
I have some queries on the updated content:
1. Earlier, Apache web site always used to show 2 Cassandra versions - one
which is "most stable" (production-ready) and other for development use. Now, I
can't see that "most stable"(production-ready) tag on any version.
Site says "The latest tick-tock release is 3.2"
As per the tick-tock logic, Does that mean 3.1 is the latest most stable
Cassandra version available today as it had bug-fixes for 3.0 ? Is 3.1
production ready? If NO, then how would production users on earlier releases
get indication on their next upgrade version e.g. 3.x or 2.2 ?
2. I am assuming that going forward EOL announcements will be published at the
Apache web site before hand just like some other Apache projects do. Is that
assumption valid?
It will certainly help to get such insights before hand on Apache site so that
community users can prepare their upgrade road map.
ThanksAnuj
On Sunday, 17 January 2016 12:48 AM, Anuj Wadehra <anujw_2...@yahoo.co.in>
wrote:
Hi Jonathan
It would be really nice if you could share your thoughts on the four points
raised regarding the Cassandra EOL process. I think similar things happen for
other open source products and it would be really nice if we could streamline
such things for Apache Cassandra.
ThanksAnuj
Sent from Yahoo Mail on Android
On Thu, 14 Jan, 2016 at 11:28 pm, Anuj Wadehra<anujw_2...@yahoo.co.in> wrote:
Hi Jonathan,
Thanks for the crisp communication regarding the tick tock release & EOL.
I think its worth considering some points regarding EOL policy and it would be
great if you can share your thoughts on below points:
1. EOL of a release should be based on "most stable"/"production ready"
version date rather than "GA" date of subsequent major releases.
2. I think we should have "Formal EOL Announcement" on Apache Cassandra
website.
3. "Formal EOL Announcement" should come at least 6 months before the EOL, so
that users get reasonable time to upgrade.
4. EOL Policy (even if flexible) should be stated on Apache Cassandra website
EOL thread on users mailing list ended with the conclusion of raising a
Wishlist JIRA but I think above points are more about working on policy and
processes rather than just a wish list.
ThanksAnuj
Sent from Yahoo Mail on Android
On Thu, 14 Jan, 2016 at 10:57 pm, Jonathan Ellis<jbel...@gmail.com> wrote:
Hi Maciek,
First let's talk about the tick-tock series, currently 3.x. This is pretty
simple: outside of the regular monthly releases, we will release fixes for
critical bugs against the most recent bugfix release, the way we did
recently with 3.1.1 for CASSANDRA-10822 [1]. No older tick-tock releases
will be patched.
Now, we also have three other release series currently being supported:
2.1.x: supported with critical fixes only until 4.0 is released, projected
in November 2016 [2]
2.2.x: maintained until 4.0 is released
3.0.x: maintained for 6 months after 4.0, i.e. projected until May 2017
I will add this information to the releases page [3].
[1]
https://mail-archives.apache.org/mod_mbox/incubator-cassandra-user/201512.mbox/%3CCAKkz8Q3StqRFHfMgCMRYaaPdg+HE5N5muBtFVt-=v690pzp...@mail.gmail.com%3E
[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...@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 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.
>
> [1]: http://www.mail-archive.com/user@cassandra.apache.org/msg45324.html
> [2]: http://www.planetcassandra.org/blog/cassandra-2-2-3-0-and-beyond/
> [3]: http://www.postgresql.org/support/versioning/
>
--
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder, http://www.datastax.com
@spyced
