> 2-4 are bad enough risks that it's worth taking the time to get it
> right before committing it.
So what is the plan for "getting it right" then?
Is it a plan that satisfies all parties?
Can people work together on that plan?
Would be great to discuss the details on the dev list (not in JIRAs)
Cassandra is out of incubation and I am no longer on the PMC ...but this
a little concerning.
I know this discussion is all about good internal design but - for the sake
of the community - isn't there a way this fork could be avoided? I don't have
the feeling this is about the work involved implem
I cannot say anything about the implementation details of the patch or
even the two different approaches. Not sure that even matters that
much at this stage. What can say though is that I got the feeling that
there is a lot of desire and drive in the community to get at least
something in. Ignoring
It certainly would be nice to have it in the main Debian repo. On the
other hand I don't think it's too much to ask to just add a line to
the sources.list and have all the freedom of the world. I am
personally not a huge fan of the Debian policy when it comes down to
jars and java. It's just that s
