incubator-cassandra-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jonathan Shook <>
Subject Re: Maintenance releases
Date Mon, 14 Feb 2011 15:54:18 GMT
As a user, this sounds like great news. To see the consensus on this
issue is reassuring.

For me, release stability and planning are more important that new
features. I would rather wait longer for the features if it means I'm
getting a solid release. It would be great if there were some clearing
of the air with respect to release discipline going forward.  Granted,
there was a time when everybody expected there to be hard and fast
changes, as Cassandra was relatively new on the landscape. I think we
are past that expectation now, or at least to the knee of the curve.

On Fri, Feb 11, 2011 at 1:36 PM, Jeremy Hanna
<> wrote:
> strong unbinding +1 :)
> I think that there were several lessons learned in the 0.6.x line about walking that
line.  Wrt regression testing, hopefully the distributed tests (thanks Stu and Kelvin and
others!) will act as a core for something like that.  I would imagine that heavy loads can
be utilized in there as well.
> On Feb 11, 2011, at 12:19 PM, Jake Luciani wrote:
>> +1
>> I'm also concerned with our lack of regression testing.  A lot of this is
>> done by individual committers firing up EC2 clusters and running basic
>> sanity checks and workloads.  Most of the bugs we are finding pop up under
>> heavy load.
>> It would be great if the community could identify and contribute use cases
>> that could be bundled into a regression test suite.
>> On Fri, Feb 11, 2011 at 11:35 AM, Gary Dusbabek <> wrote:
>>> I've been uncomfortable with the amount of features I perceive are
>>> going into our maintenance releases for a while now.  I thought it
>>> would stop after we committed ourselves to having a more predictable
>>> major release schedule.  But getting 0.7.1 out feels like it's taken a
>>> lot more effort than it should have.  I wonder if part of the problem
>>> is that we've been committing destabilizing features into it?  IMO,
>>> maintenance releases (0.7.1, 0.7.2, etc.) should only contain bug
>>> fixes and *carefully* vetted features.
>>> I've scanned down the list of 0.7.1 changes in CHANGES.txt and about
>>> half of them are features that I think could have stayed in trunk.  I
>>> think we did this a lot with the early maintenance releases of 0.6 as
>>> well, probably in an effort to get features out *now* instead of
>>> waiting for an 0.7 that was not happening soon enough.  We've decided
>>> to pick up the pace of our major release schedule (sticking to four
>>> months).  I think maintaining this pace will be difficult if we
>>> continue to commit as many features into the minor releases as we have
>>> been.
>>> I'm willing to concede that I may have an abnormally conservative
>>> opinion about this.  But I wanted to voice my concern in hopes we can
>>> improve the quality and delivery of our maintenance releases.
>>> Gary.

View raw message