Should I merge the fix to just the 3.0.10 tag? or should we include the 3 new tickets that went into 3.0.11 already? I see no issue with the latter since they are bugfixes
On Fri, Nov 11, 2016 at 8:48 AM, Jake Luciani <jak...@gmail.com> wrote: > -1 due to https://issues.apache.org/jira/browse/CASSANDRA-11039 > > It's a small fix but a critical bug. I'll patch shortly > > On Nov 11, 2016 2:32 AM, "Tommy Stendahl" <tommy.stend...@ericsson.com> > wrote: > >> +1 (non-binding) >> >> >> On 2016-11-08 21:08, Michael Shuler wrote: >> >>> I propose the following artifacts for release as 3.0.10. >>> >>> sha1: 4e0bced5e6a82ebd22b074b8ef96d930c5f3159d >>> Git: >>> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=sho >>> rtlog;h=refs/tags/3.0.10-tentative >>> Artifacts: >>> https://repository.apache.org/content/repositories/orgapache >>> cassandra-1132/org/apache/cassandra/apache-cassandra/3.0.10/ >>> Staging repository: >>> https://repository.apache.org/content/repositories/orgapache >>> cassandra-1132/ >>> >>> The Debian packages are available here: http://people.apache.org/~mshu >>> ler >>> >>> The vote will be open for 72 hours (longer if needed). >>> >>> [1]: (CHANGES.txt) https://goo.gl/mnmZgI >>> [2]: (NEWS.txt) https://goo.gl/F1kAmR >>> >>> >> -- http://twitter.com/tjake
