On Sat, 2010-06-05 at 01:38 +0000, Robert Edmonds wrote: > On 2010-06-04, Eric Evans <eev...@rackspace.com> wrote: > > So, the bigger problem here would seem to be one of long-term > support. > > In other words, trying to find common ground between release cycles. > > > > I am (have been) interested in uploading Cassandra to the Debian > > archives, so let's use that as an example: > > as a debian developer and a cassandra user, i don't think it makes > much sense for cassandra to go into stable releases given its current > rate of development. i also don't think cassandra is suited for > volatile (or even volatile-sloppy) or backports.
Right, this was my thinking as well. My remarks about volatile and backports were in reference to some possible future where Cassandra development had slowed enough to consider including it in a stable release, yet still outpaced Debian release cadence. > i think the best possible solution would be for cassandra to be > maintained as a release quality package in debian unstable, with all > external java dependencies packaged separately and available in debian > unstable as well, but the cassandra package itself should be prevented > from migrating to testing and kept out of stable. Yup. I mentioned precisely this to Clint Byrum on IRC yesterday. Unfortunately, I don't think there is a comparable path that would satisfy his requirements for Ubuntu. So Robert, I am DD as well, and so is Paul Cannon who chimed in earlier in the discussion. As a Debian Developer and Cassandra user, would you be interested in joining The Cause? :) -- Eric Evans eev...@rackspace.com
