Re: DataStax and Cassandra

[Alain RODRIGUEZ]

Hi,

On a personal note, I’d like to thank those in this weekend’s threads who have
> tried to de-escalate tensions rather than inflame them.


I agree. Thanks. Let's try to all learn from that, please. I believe we can
disagree politely and respectfully. And we must do so. We can still express
anything we want to express. It's just a bit harder, it takes a bit longer
this way, but it's so much more efficient to have your real message
reaching people.

Jeff Jirsa’s diplomacy stands out to me as particularly mature.
>

True, that was my opinion as well while reading the threads. I also want to
take the chance to say that this applies to you as well Jonathan. IMHO,
your message is just what the community needed right now. So thanks for the
clarification...

... And for what you have done in the last years. As Aaron said at the
Summit, you, as an individual, have changed my life, and many other, in a
very good way. From my first message in the user mailing list you answered
to this last message in the dev list to preserve the community, even after
stepping down from the project chair. The amount, variety and quality of
work you have done and the way you are behaving are inspiring for me.

As has been said before, we’re all on the same team here.  Now let’s get back
> to making Apache Cassandra the best open source distributed database in
> the world!


Sounds good :-).

A community is nothing but what we bring to it as individuals. Looking
forward to working all together, with our disagreements, but peacefully, in
the same direction, once again.

C*heers,
---
Alain Rodriguez - @arodream - al...@thelastpickle.com
France

The Last Pickle - Apache Cassandra Consulting
http://www.thelastpickle.com

2016-11-06 21:43 GMT+01:00 Jonathan Ellis :

> Hi all,
>
> There’s been some conversation and some acrimony kicked up by my recent
> blog post here
> .
> I appreciate the conversation and regret the acrimony!
>
> Fundamentally I was trying to convey two complementary messages:
>
>
>1.
>
>DataStax wants to see Apache Cassandra thrive and will continue to
>contribute in multiple ways to make that happen, but at the same time
>2.
>
>DataStax will be placing more emphasis on DSE and more engineering
>effort behind it.
>
>
> It’s unfortunate that the timing here coincides with some regrettable
> actions by the Apache Board of Directors, but this change in emphasis is
> primarily driven by business factors unrelated to the ASF.  DataStax shares
> Apache’s commitment to community-led development independent of any single
> vendor.
>
> One friend pointed out to me that any vagueness can be interpreted as
> “weasel words” and turned into alarmist conjectures as to what this really
> means.  I gave several specifics in the post as to how DataStax will
> continue to contribute to Apache Cassandra, but maybe I can simplify
> things:
>
> This has been going on for months.  DataStax’s level of contribution moving
> forward will be nearly indistinguishable from our level in October and
> September.  If that was no cause for alarm then, I hope it will not be
> cause for alarm now that we have articulated how we are moving forward.
>
> To be explicit: DataStax engineers will continue to contribute code
> reviews, bug fixes, and selected new features to Apache Cassandra.  In a
> qualitative sense then, you could almost say that nothing has changed.
>
> On a personal note, I’d like to thank those in this weekend’s threads who
> have tried to de-escalate tensions rather than inflame them.  Jeff Jirsa’s
> diplomacy stands out to me as particularly mature.
>
> As has been said before, we’re all on the same team here.  Now let’s get
> back to making Apache Cassandra the best open source distributed database
> in the world!
>
> --
> Jonathan Ellis
> co-founder, http://www.datastax.com
> @spyced
>

DataStax and Cassandra

[Jonathan Ellis]

Hi all,

There’s been some conversation and some acrimony kicked up by my recent
blog post here
.
I appreciate the conversation and regret the acrimony!

Fundamentally I was trying to convey two complementary messages:


   1.

   DataStax wants to see Apache Cassandra thrive and will continue to
   contribute in multiple ways to make that happen, but at the same time
   2.

   DataStax will be placing more emphasis on DSE and more engineering
   effort behind it.


It’s unfortunate that the timing here coincides with some regrettable
actions by the Apache Board of Directors, but this change in emphasis is
primarily driven by business factors unrelated to the ASF.  DataStax shares
Apache’s commitment to community-led development independent of any single
vendor.

One friend pointed out to me that any vagueness can be interpreted as
“weasel words” and turned into alarmist conjectures as to what this really
means.  I gave several specifics in the post as to how DataStax will
continue to contribute to Apache Cassandra, but maybe I can simplify things:

This has been going on for months.  DataStax’s level of contribution moving
forward will be nearly indistinguishable from our level in October and
September.  If that was no cause for alarm then, I hope it will not be
cause for alarm now that we have articulated how we are moving forward.

To be explicit: DataStax engineers will continue to contribute code
reviews, bug fixes, and selected new features to Apache Cassandra.  In a
qualitative sense then, you could almost say that nothing has changed.

On a personal note, I’d like to thank those in this weekend’s threads who
have tried to de-escalate tensions rather than inflame them.  Jeff Jirsa’s
diplomacy stands out to me as particularly mature.

As has been said before, we’re all on the same team here.  Now let’s get
back to making Apache Cassandra the best open source distributed database
in the world!

-- 
Jonathan Ellis
co-founder, http://www.datastax.com
@spyced

Re: Datastax including Cassandra 3.0

[Yoshi Kimoto]

Also FYI
http://docs.datastax.com/en/landing_page/doc/landing_page/compatibility.html

On 2016/05/10 17:02, DuyHai Doan wrote:

The next major release of Datastax Enterprise 5.0 will include C* 3.x. It
is expected to be released somewhere around June/July, no exact date has
been announced yet.
Le 10 mai 2016 09:08, "Joly, Josselin"  a écrit :


Hello,

I am wondering if the version of Cassandra 3.0 is already included in the
lastest version of Datastax entreprise, do you know somthing about it ?


Best regards,

Josselin Joly.

[cpu_time.png]

Re: Datastax including Cassandra 3.0

[DuyHai Doan]

The next major release of Datastax Enterprise 5.0 will include C* 3.x. It
is expected to be released somewhere around June/July, no exact date has
been announced yet.
Le 10 mai 2016 09:08, "Joly, Josselin"  a écrit :

> Hello,
>
> I am wondering if the version of Cassandra 3.0 is already included in the
> lastest version of Datastax entreprise, do you know somthing about it ?
>
>
> Best regards,
>
> Josselin Joly.
>
> [cpu_time.png]
>

Datastax including Cassandra 3.0

[Joly, Josselin]

Hello,

I am wondering if the version of Cassandra 3.0 is already included in the 
lastest version of Datastax entreprise, do you know somthing about it ?


Best regards,

Josselin Joly.

[cpu_time.png]