Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
Subject: Re: 0.7 release
From: Eric Evans <eevans@rackspace.com>
To: user@cassandra.apache.org
In-Reply-To: <AANLkTimCN4dDSaBZufuk5Z5GYAh3n=QyPb9aSbdc9yav@mail.gmail.com>
References: <AANLkTimCN4dDSaBZufuk5Z5GYAh3n=QyPb9aSbdc9yav@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Date: Fri, 15 Oct 2010 10:59:44 -0500
Message-ID: <1287158384.10982.109.camel@erebus.lan>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit

On Thu, 2010-10-14 at 13:07 -0700, Chris Oei wrote:
> Also, once 0.7 is officially released, will 0.6 still be maintained
> (sort of like Ubuntu's long-term releases), or will all 0.6
> development stop? 

Speaking with my Release Manager hat on, I would be willing to commit to
producing some additional 0.6 releases after 0.7, providing there were
release-worthy changes merged to that branch.

"Release-worthy changes" is really the key though because you need
people willing to back-port important fixes, people to merge them, and
enough testing and feedback to avoid nasty regressions, (and of course
you need consensus from the rest of the project that long(ish)-term
support doesn't interfere with the project's goals).

So far there hasn't been sufficient interest to pursue this, and old
stable releases have become dead-branches as soon as a new stable
release is made.

-- 
Eric Evans
eevans@rackspace.com