> 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.
(speaking now from the perspective of a consumer, disregarding the implications on development) I don't think you're being conservative. In particular in light of the recent 1.0 discussion and whether or not to signal that Cassandra is "ready" and no longer needing committers on staff etc; having solid releases is probably an important part of instilling confidence in the project and decreasing the risk associated with adopting a new release. For example, from the point of view of the user, I think that things like CASSANDRA-1992 should preferably result in an almost immediate bugfix-only release with instructions and impact information for users. Being only a very minor contributor I don't have a full grasp of the implications on the agility of development that a change would have, but certainly I think that if a goal is to have users feel more confident (and in fact be safer) in using a Cassandre release without careful monitoring of the mailing lists and JIRA, adjusting the release engineering a bit seems like a high-priority change towards that goal. -- / Peter Schuller
