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 Shuler <mich...@pbandjelly.org> 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: > https://repository.apache.org/content/repositories/orgapachecassandra-1171/org/apache/cassandra/apache-cassandra/3.0.18/ > Staging repository: > https://repository.apache.org/content/repositories/orgapachecassandra-1171/ > > The Debian and RPM packages are available here: > http://people.apache.org/~mshuler > > The vote will be open for 72 hours (longer if needed). > > [1]: CHANGES.txt: > https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/3.0.18-tentative > [2]: NEWS.txt: > https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/3.0.18-tentative > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org