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.
I was not referring to Enterprise support here. When I said Open source
"product" by mistake, I was just referring to some other Apache open source
projects like Apache Cassandra where you get EOL announcements, info etc on the
main Apache web site. I think all four points are very relevant in c
Correct, this is an open source project.
If you want a Enterprise support story Datastax has an Enterprise option for
you.
> On Jan 16, 2016, at 11:19 AM, Anuj Wadehra wrote:
>
> Hi Jonathan
>
> It would be really nice if you could share your thoughts on the four points
> raised regarding
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
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.
On Thu, Jan 14, 2016 at 5:56 PM, Jack Krupansky
wrote:
> Thanks, Jonathan. The end-of-life (EOL) question is still dangling out
> there
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 4:26 PM, Jack Krupans
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 that look like the old ones
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
And in general, 3.x (x != 0) will be maintained until (and does x
even vs. odd affect the rule)
And what exactly is the general rule/criteria for when 3.x will be
conside
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"
vers
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 re
Mark, what would the policy dictate if the bug is in a feature that was
introduced in 3.x and the feature wasn't in 3.0 and the current release is
3.x+k where k is greater than two - technically 3.x is no longer supported,
so does that mean no backporting of the fix and only 3.x+k+1 would get the
b
Let's do a couple examples:
1. Current release: 3.4.0, bug found in 3.1.0 that also exists in
subsequent versions; the bug fix will be ported back to 3.0.x and 3.5.0.
2. Current release 3.3.0, bug found in 3.3.0; the bug fix will be ported
back to 3.0.x and 3.4.0. In rare cases, a 3.3.
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.
13 matches
Mail list logo
