been uncomfortable with the amount of features I perceive are
going into our maintenance releases for a while now. I thought it
would stop after we committed ourselves to having a more predictable
major release schedule. But getting 0.7.1 out feels like it's taken a
lot more effort than
On Fri, Feb 11, 2011 at 8:35 AM, Gary Dusbabek gdusba...@gmail.com wrote:
I've been uncomfortable with the amount of features I perceive are
going into our maintenance releases for a while now. [...] IMO,
maintenance releases (0.7.1, 0.7.2, etc.) should only contain bug
fixes and *carefully
I've been uncomfortable with the amount of features I perceive are
going into our maintenance releases for a while now. I thought it
would stop after we committed ourselves to having a more predictable
major release schedule. But getting 0.7.1 out feels like it's taken a
lot more effort than
On Fri, Feb 11, 2011 at 8:35 AM, Gary Dusbabek gdusba...@gmail.com wrote:
I've been uncomfortable with the amount of features I perceive are
going into our maintenance releases for a while now. I thought it
would stop after we committed ourselves to having a more predictable
major release
perceive are
going into our maintenance releases for a while now. I thought it
would stop after we committed ourselves to having a more predictable
major release schedule. But getting 0.7.1 out feels like it's taken a
lot more effort than it should have. I wonder if part of the problem
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
On Fri, Feb 11, 2011 at 11:07 AM, Peter Schuller
peter.schul...@infidyne.com wrote:
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.
+1.
Cassandra has matured a lot lately and more users are relying heavily on it in
production. For those users, including us, stability and predictability becomes
very important.
Not including new and potentially unstable features in maintenance releases is
an easy way to decrease risk
and contribute use cases
that could be bundled into a regression test suite.
On Fri, Feb 11, 2011 at 11:35 AM, Gary Dusbabek gdusba...@gmail.com wrote:
I've been uncomfortable with the amount of features I perceive are
going into our maintenance releases for a while now. I thought it
would stop after
are
going into our maintenance releases for a while now. I thought it
would stop after we committed ourselves to having a more predictable
major release schedule. But getting 0.7.1 out feels like it's taken a
lot more effort than it should have. I wonder if part of the problem
is that we've
10 matches
Mail list logo
