On 05/12/2017 01:11 PM, Gopal, Dhruva wrote:
> Since, we’re trying to qualify this for Production, 3.11 isn’t
> officially released, yet is it – it’s why we’re planning on using
> 3.10. The concern stems from the build failing with byteman. We’re
> novices at building our own rpms for Cassandra and are concerned that
> there may be other issues with the 3.10 release and maybe we should
> hold off till 3.11 is released and ready. Any opinions/feedback will
> help.

Here's the current changelog from 3.10 -> 3.11.0
https://github.com/apache/cassandra/blob/cassandra-3.11/CHANGES.txt#L1-L115

That's a lot of fixed bugs since 3.10, so use that information as you
see fit.

The 3.11.0 release is currently down to making test fixes and/or
tracking down the last few remaining bugs, if test failures are due to
actual bugs.

The 3.11.X release series will be a long-term maintenance branch, so
fixes will be ongoing in this branch and new releases of 3.11.X will be
made when needed.

If you are working on evaluating a release for production, I would
suggest that evaluating 3.11.0 now would be a better choice, and your
byteman issues are already fixed in-tree, so no hacking around and doing
your own thing. 3.10 won't ever get updated, so if you need fixes for
issues you might find there, the path would be to upgrade to 3.11.X
anyway, so it doesn't make sense to me to start on 3.10.

If you have additional RPM package fixes for the cassandra-3.11 branch
and want to get them in for the 3.11.0 release, please include those on:
https://issues.apache.org/jira/browse/CASSANDRA-13433

Want to build RPMS easily and directly from git branches? This is where
the project is working on that build infrastructure to streamline
releases, and can be used to build packages on your own. See the README on:
https://github.com/apache/cassandra-builds

-- 
Kind regards,
Michael Shuler

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
For additional commands, e-mail: user-h...@cassandra.apache.org

Reply via email to