cassandra-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Kjellman <mkjell...@internalcircle.com>
Subject Re: Proposal: release 2.2 (based on current trunk) before 3.0 (based on 8099)
Date Mon, 11 May 2015 22:56:02 GMT
Last I checked — and I could be wrong — we’ve never had to think about what to number
a Cassandra version due to a ticket that could “impact” our users so dramatically due
to the scope of the changes from a single ticket. Food for thought.

love,
kjellman

> On May 11, 2015, at 2:20 PM, Alex Popescu <alexp@datastax.com> wrote:
> 
> On Mon, May 11, 2015 at 2:16 PM, Jonathan Haddad <jon@jonhaddad.com> wrote:
> 
>> I'm not sure if the complications surrounding the versioning of the drivers
>> should be factored into the releases of Cassandra.
> 
> 
> I agree. If we could come up with a versioning scheme that would also work
> for drivers, that would be
> the ideal case as it will prove quite helpful to our users.
> 
> 
>> I think that 3.0
>> signals a massive change and calling the release containing 8099 a .1 would
>> be drastically underplaying how big of a release it is - from the
>> perspective of the end user it would be a disservice.
>> 
>> 
> I see. My last suggestion could work though as it signals both releases
> having significant impact.
> 
> 
> 
>> 
>> On Mon, May 11, 2015 at 2:09 PM Jonathan Ellis <jbellis@gmail.com> wrote:
>> 
>>> I do like 2.2 and 3.0 over 3.0 and 3.1 because going from 2.x to 3.x
>>> signals that 8099 really is a big change.
>>> 
>>> On Mon, May 11, 2015 at 3:28 PM, Alex Popescu <alexp@datastax.com>
>> wrote:
>>> 
>>>> On Sun, May 10, 2015 at 2:14 PM, Robert Stupp <snazy@snazy.de> wrote:
>>>> 
>>>>> Instead of labeling it 2.2, I’d like to propose to label it 3.0 (so
>>>>> basically just move 8099 to 3.1).
>>>>> In the end it’s ”only a label”. But there are a lot of new
>> user-facing
>>>>> features in it that justifies a major release.
>>>>> 
>>>> 
>>>> +1 on labeling the proposed 2.2 as 3.0 and moving (8099 to 3.1)
>>>> 
>>>> 1. Tons of new features that feel more than just a 2.2
>>>> 2. The majority of features planned for 3.0 are actually ready for this
>>>> version
>>>> 3. in order to avoid compatiblity questions (and version compatibility
>>>> matrices), the drivers developed by DataStax have
>>>>    followed the Cassandra versions so far. The Python and C# drivers
>> are
>>>> already at 2.5 as they added some major features.
>>>> 
>>>>   Renaming the proposed 2.2 as 3.0 would allow us to continue to use
>>> this
>>>> versioning policy until all drivers are supporting
>>>>   the latest Cassandra version and continue to not require a user to
>>> check
>>>> a compatibility matrix.
>>>> 
>>>> 
>>>> --
>>>> Bests,
>>>> 
>>>> Alex Popescu | @al3xandru
>>>> Sen. Product Manager @ DataStax
>>>> 
>>> 
>>> 
>>> 
>>> --
>>> Jonathan Ellis
>>> Project Chair, Apache Cassandra
>>> co-founder, http://www.datastax.com
>>> @spyced
>>> 
>> 
> 
> 
> 
> -- 
> Bests,
> 
> Alex Popescu | @al3xandru
> Sen. Product Manager @ DataStax

Mime
View raw message