+1, and also see no point in EOL; if we have failed to back port something important, we should rectify it.
> On 6 Feb 2019, at 05:09, Jeff Jirsa <jji...@gmail.com> wrote: > > +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 <mich...@pbandjelly.org> > wrote: > >> *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=refs/tags/2.1.21-tentative >> Artifacts: >> >> https://repository.apache.org/content/repositories/orgapachecassandra-1173/org/apache/cassandra/apache-cassandra/2.1.21/ >> Staging repository: >> https://repository.apache.org/content/repositories/orgapachecassandra-1173/ >> >> 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/2.1.21-tentative >> [2]: NEWS.txt: >> >> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/2.1.21-tentative >> >> --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org
