Hi Fumiya, I'm looking at it this week.
Dinesh
On Sunday, February 3, 2019, 9:46:35 PM PST, Fumiya Yamashita
wrote:
Hello.
I have created a ticket for the improvement of nodetool.
(https://issues.apache.org/jira/browse/CASSANDRA-14847)
I’d like this patch to be merged to Cassandra 4.
We currently intent to support 2.1 with critical fixes only, which
leaves some room for interpretation. As usually, people have different
views, in this case on what exactly a critical fix is. If there are some
patches that are potential candidates for 2.1, but haven’t been
committed, then we s
Not sure we need another 2.1 release, this one included, but sure, +1
So long as the branch itself stays kinda open and most critical issues can have
at least fixes for them committed, the interested parties can then keep
building the artefacts manually.
Once 4.0 is out we can freeze the branch
+1
> On 3 Feb 2019, at 00:32, Michael Shuler wrote:
>
> I propose the following artifacts for release as 2.2.14.
>
> sha1: af91658353ba601fc8cd08627e8d36bac62e936a
> Git:
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.2.14-tentative
> Artifacts:
> https://reposit
+1
> On 4 Feb 2019, at 00:39, Joseph Lynch wrote:
>
> 3.0.18-tentative unit and dtest run:
> https://circleci.com/gh/jolynch/cassandra/tree/3.0.18-tentative
>
> unit tests: 0 failures
> dtests: 1 failure
> * test_closing_connections - thrift_hsha_test.TestThriftHSHA (
> https://issues.apache.or
+1
> On 3 Feb 2019, at 00:31, Michael Shuler wrote:
>
> I propose the following artifacts for release as 3.11.4.
>
> sha1: fd47391aae13bcf4ee995abcde1b0e180372d193
> Git:
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.11.4-tentative
> Artifacts:
> https://reposit
