Re: [DISCUSS] CEP-65: cassaudra-utils - A shared utility library for the cassandra ecosystem

[Mick]

> Changes to libraries that fix one consumer can 
> break another: we will need to be able to build and run tests for all 
> dependent projects when we make changes


I agree with Benedict here.
This testing matrix has to be done, and the earlier it is done (and done by the 
author) the better.
If we're honest about that, then the API labelling and versioning isn't needed.

Pushing the complication onto the consumer in following such api labelling and 
versions, and then finding out late things don't work for them and another 
change in the utils repo is needed, doesn't sound fun.  Let's just keep it 
simple and encourage everyone to say close, via authors taking full 
responsibility for a change they make at such low-level and shared code.