There’s SO MUCH that needs to go out, let’s just get out what we have
--
Jeff Jirsa
> On Feb 2, 2019, at 5:35 PM, Benedict Elliott Smith
> wrote:
>
> CASSANDRA-14812 should probably land in this release, given that it is a
> critical bug, has been patch available for a while, and is relati
CASSANDRA-14812 should probably land in this release, given that it is a
critical bug, has been patch available for a while, and is relatively simple.
That said, we are sorely due a release. But if we go ahead without it, we
should follow up soon after.
> On 3 Feb 2019, at 00:32, Michael Shul
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://repository.apache.org/content/repositories/orgapachecassandra-1170/org/apache/
I propose the following artifacts for release as 3.0.18.
sha1: edd52cef50a6242609a20d0d84c8eb74c580035e
Git:
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.18-tentative
Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1171/org/apache/
*EOL* release for the 2.1 series. There will be no new releases from the
'cassandra-2.1' branch after this release.
I propose the following artifacts for release as 2.1.21.
sha1: 9bb75358dfdf1b9824f9a454e70ee2c02bc64a45
Git:
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=r
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://repository.apache.org/content/repositories/orgapachecassandra-1172/org/apache/
Hello.
Can someone provide feedback for
https://issues.apache.org/jira/browse/CASSANDRA-14706 ?
Thank you.
-
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apach
