Re: Cassandra 2.2, 3.0, and beyond

On Thu, Jun 11, 2015 at 6:56 PM, Mohammed Guller wrote: > By that logic, 2.1.0 should have been somewhat as stable as 2.0.10 (the > last release of 2.0.x branch before 2.1.0). However, we found out that it > took almost 9 months for 2.1.x series to become stable and suitable for > production. G

Re: Cassandra 2.2, 3.0, and beyond

We've started using the docs-impacting label to make it easier for the technical writers to keep up, but otherwise we're not planning any major changes. On Thu, Jun 11, 2015 at 4:50 AM, Dan

RE: Cassandra 2.2, 3.0, and beyond

time for 2.2 to become stable. Mohammed From: graham sanderson [mailto:gra...@vast.com] Sent: Thursday, June 11, 2015 6:34 PM To: user@cassandra.apache.org Subject: Re: Cassandra 2.2, 3.0, and beyond I think the point is that 2.2 will replace 2.1.x + (i.e. the done/safe bits of 3.0 are included

Re: Cassandra 2.2, 3.0, and beyond

> 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 <mailto:jbel...@gmail.com>] > Sent: Thursday, June 11, 2015 10:14 AM > To: user > S

RE: Cassandra 2.2, 3.0, and beyond

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 mailto:pierredev...@gmail.com>> wrote: Hi, 3.x beta release date ? 2015-06-11 16:21 GMT+02:00 Jonathan Ellis mailto:jbel...@gmail.com>>: 3.1 is EOL as soon as 3.3 (the

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 wrote: > Hi, > > 3.x beta release date ? > > 2015-06-11 16:21 GMT+02:00 Jonathan Ellis : > >> 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 < >> st

Re: Cassandra 2.2, 3.0, and beyond

Hi, 3.x beta release date ? 2015-06-11 16:21 GMT+02:00 Jonathan Ellis : > 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> wrote: > >> > We are also extending our backwards compatibility polic

Re: Cassandra 2.2, 3.0, and beyond

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> 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.

Re: Cassandra 2.2, 3.0, and beyond

Hi Jonathan Does documentation fit into the new monthly releases and definition of done as well, or is that part of another process? I didn't see any mention of it in the docs, though I may have missed it. On Thu, 11 Jun 2015 at 9:10 pm Stefan Podkowinski < stefan.podkowin...@1und1.de> wrote: > >

Re: Cassandra 2.2, 3.0, and beyond

> 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 a

Re: Cassandra 2.2, 3.0, and beyond

On Wed, Jun 10, 2015 at 1:43 PM, wrote: > With 3.0, what happens to existing Thrift-based tables (with dynamic > column names, etc.)? Just like in Cassandra 2.x, they will show up as COMPACT STORAGE tables in a format that CQL can work with. We're making a few adjustments to how the schema is

RE: Cassandra 2.2, 3.0, and beyond

With 3.0, what happens to existing Thrift-based tables (with dynamic column names, etc.)? Sean Durity From: Jonathan Ellis [mailto:jbel...@gmail.com] Sent: Wednesday, June 10, 2015 10:30 AM To: user Subject: Cassandra 2.2, 3.0, and beyond As you know, we've split our post-2.1 release int

Cassandra 2.2, 3.0, and beyond

*As you know, we've split our post-2.1 release into two pieces, with 2.2 to be released in July (rc1 out Monday ) and 3.0 in September.2.2 will include Windows support, commitlog compression , JSON support