+1
On Sat, Feb 2, 2019 at 4:32 PM Michael Shuler
wrote:
> 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:
>
>
+1
On Sat, Feb 2, 2019 at 4:32 PM 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:
>
>
+1 (to the release, I see no reason to force this to be EOL; leaving the
branch open has zero cost, and if a serious enough patch comes up, we'll
likely be happy we have the option to fix it).
On Sat, Feb 2, 2019 at 4:32 PM Michael Shuler
wrote:
> *EOL* release for the 2.1 series. There will
+1
On Sat, Feb 2, 2019 at 4:38 PM 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:
>
>
Hi,
Can we also run the upgrade tests? We should do that as part of the release
process. I can do that tomorrow.
Ariel
On Tue, Feb 5, 2019, at 1:11 PM, Joseph Lynch wrote:
> 2.2.14-tentative unit and dtest run:
> https://circleci.com/gh/jolynch/cassandra/tree/2.2.14-tentative
>
> unit tests:
2.2.14-tentative unit and dtest run:
https://circleci.com/gh/jolynch/cassandra/tree/2.2.14-tentative
unit tests: 0 failures
dtests: 5 failures
* test_closing_connections - thrift_hsha_test.TestThriftHSHA (
https://issues.apache.org/jira/browse/CASSANDRA-14595)
* test_multi_dc_tokens_default -
>
> I propose the following artifacts for release as 2.1.21.
>
+1 for this release of 2.1.21
Comments:
- we don't really need the checksums on gpg signature files. (Previously
releases are also doing this.) I believe they can just be manually deleted from
the staging nexus repository.
