Hi John, I work for the DSE team. What you're seeing is the result of DSE having its own release schedule distinct from Apache Cassandra. We'll start qualifying an Apache release to build on, such as 3.0.7 for DSE 5.0, but if 3.0.8 comes out while we're still working on 5.0.1 we won't necessarily restart that QA process. Often it makes more sense to take selected changes from that release instead.
Or, sometimes our customers will find an issue before the Apache community, and we'll ship a hotfix version of DSE with a fix that goes into a subsequent Apache release. Either way, all our fixes do get contributed to the community, and we publish a list of changes compared to the Apache release we built on, e.g. [1] and [2] for DSE 4.8 and 5.0. We also include Apache Solr and Apache Spark in DSE and follow the same processes for those projects. [1] https://docs.datastax.com/en/datastax_enterprise/4.8/datastax_enterprise/RNcassChanges.html?scroll=RNcassFixes__488_unique_1 [2] https://docs.datastax.com/en/latest-dse/datastax_enterprise/RNcassChanges.html?scroll=RNcassFixes__500_unique_1 Jeremiah Jordan Lead Software Engineer DSE DataStax, Inc. > On Jul 21, 2016, at 10:22 AM, John John <john.s.1...@mail.com> wrote: > > > > What is the difference behind Datastax DSE Cassandra and open source. > > 1. Why is Datastax maintaining a fork of open source where they back port > fixes which are not back ported for the community for that version. People > running DSE wants more stability thats why? > > 2. I know community moved to a new release process which will make it very > hard for companies to use open source. I have been told DSE will still have > long term support for release similar to old release process? > > I am very happy to use DSE since it gives more features but was confused why > we are in this situation. I am sure I am missing something.
