+1 non-binding
Commit that CR to cassandra-2.0 branch HEAD, leaving the tag where it is
and I can build DSC with it included :)
--
Michael
On 09/17/2015 08:48 AM, Jake Luciani wrote:
I'm not inclined to re-roll for a missing CR but if others feel strongly
about it I will do it.
On Wed, Sep 16, 2015 at 10:04 PM, Brandon Williams <dri...@gmail.com> wrote:
So, I made a small mistake:
https://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=commitdiff;h=718e47f084019f1b22d8a66d911a6cbbcaf6483c
Obviously this will have no effect on the code, but it's kind of a problem
when you're trying to troubleshoot the type of problem I added that info
for in https://issues.apache.org/jira/browse/CASSANDRA-10330. I don't
think this requires a re-roll, but if we could release with that carriage
return it would be beneficial since there won't be another 2.0 release.
On Wed, Sep 16, 2015 at 1:29 PM, Jake Luciani <j...@apache.org> wrote:
I propose the following artifacts for release as 2.0.17.
sha1: 3aff44915edbd2bf07955d5b30fd47bf9c4698da
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.0.17-tentative
Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1078/org/apache/cassandra/apache-cassandra/2.0.17/
Staging repository:
https://repository.apache.org/content/repositories/orgapachecassandra-1078/
The artifacts as well as the debian package are also available here:
http://people.apache.org/~jake
The vote will be open for 72 hours (longer if needed).
[1]: http://goo.gl/1g0t58 (CHANGES.txt)
[2]: http://goo.gl/SHN2y3 (NEWS.txt)
