From dev-return-15417-archive-asf-public=cust-asf.ponee.io@cassandra.apache.org Mon Feb 4 16:56:32 2019 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 91635180651 for ; Mon, 4 Feb 2019 17:56:31 +0100 (CET) Received: (qmail 99278 invoked by uid 500); 4 Feb 2019 16:56:30 -0000 Mailing-List: contact dev-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cassandra.apache.org Delivered-To: mailing list dev@cassandra.apache.org Received: (qmail 99267 invoked by uid 99); 4 Feb 2019 16:56:30 -0000 Received: from mail-relay.apache.org (HELO mailrelay1-lw-us.apache.org) (207.244.88.152) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Feb 2019 16:56:30 +0000 Received: from Stefans-MacBook-Pro-home.fritz.box (ppp-93-104-79-163.dynamic.mnet-online.de [93.104.79.163]) by mailrelay1-lw-us.apache.org (ASF Mail Server at mailrelay1-lw-us.apache.org) with ESMTPSA id 345171106 for ; Mon, 4 Feb 2019 16:56:29 +0000 (UTC) Subject: Re: [VOTE] Release Apache Cassandra 2.1.21 To: dev@cassandra.apache.org References: From: Stefan Podkowinski Message-ID: <983140cd-1fdc-289e-9e21-2d91bcb465e0@apache.org> Date: Mon, 4 Feb 2019 17:56:17 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:60.0) Gecko/20100101 Thunderbird/60.5.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US 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 should revisit them and discuss back-porting. But EOL dates are not something that should be changed ad-hoc. If we do that, we might as well completely stop communicating support periods at all, since we may change our minds any time anyways, and I don’t think that’s acceptable. On 04.02.19 01:31, Michael Shuler wrote: > My first couple sentences in the vote email were intended as a > statement, based on a lack of concerns voiced on EOL of 2.1. > > I made a request for comment on EOL of 2.1 series a month ago, in > "Subject: EOL 2.1 series?": > https://lists.apache.org/thread.html/87ee2e3d13ea96744545ed8612496a93f8235747c4f60d0084b37bae@%3Cdev.cassandra.apache.org%3E > > Yes, I'm aware our download page states we support 2.1 until 4.0, but we > do not really do so. > > The reality is that developers have been actively ignoring the branch, > even when suggested to commit to the 2.1 branch. I can go dig up IRC > logs and commits, but I really don't feel like it adds any value to the > conversation. As Jonathan Haddad says, let's just be honest with users > about what has already been happening independently. > > To continue stating we actively support 2.1 until 4.0 and actually > follow through, the project should audit fixed bugs in 2.2+ and see if > they still exist in 2.1, unfixed. I imagine there are a few. I know for > sure of one that was not committed. Alternatively, we sunset the branch, > make that change on the download page, and move on. I don't think it's > right to continue telling users we are doing something, if we aren't and > haven't been. > > Michael > > On 2/3/19 5:24 PM, Anthony Grasso wrote: >> +1 non-binding, for the release of 2.1.21 >> >> Regarding EOL of 2.1.x, did we announce in the past that 2.1.21 would be >> the final release? >> >> According to the download page 2.1 >> is meant to be supported with critical fixes only until 4.0 is released. I >> suspect that people may be relying on this, as I have seen a number 2.1.x >> clusters still in production use. >> >> On Mon, 4 Feb 2019 at 07:09, Jonathan Haddad wrote: >> >>> I think having the discussion around EOL is pretty important, in order to >>> set the right expectations for the community. >>> >>> Looking at the commits for 2.1, there's hardly any activity going on, >>> meaning it's effectively been EOL'ed for a long time now. I think it's >>> better that we be honest with folks about it. >>> >>> On Sun, Feb 3, 2019 at 9:34 AM Nate McCall wrote: >>> >>>> +1 on the release of 2.1.21 (let's focus on that in the spirit of >>>> these other votes we have up right now). >>>> >>>> I don't feel the need to be absolutist about something being EOL. >>>> >>>> On Sun, Feb 3, 2019 at 1:47 AM Stefan Podkowinski >>> wrote: >>>>> What are we voting on here? Releasing the 2.1.21 candidate, or that 2.1 >>>>> would become EOL? Please let's have separate votes on that, if you want >>>>> to propose putting 2.1 EOL (which I'm strongly -1). >>>>> >>>>> >>>>> On 03.02.19 01:32, Michael Shuler 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-unsubscribe@cassandra.apache.org >>>>> For additional commands, e-mail: dev-help@cassandra.apache.org >>>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org >>>> For additional commands, e-mail: dev-help@cassandra.apache.org >>>> >>>> >>> -- >>> Jon Haddad >>> http://www.rustyrazorblade.com >>> twitter: rustyrazorblade >>> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org > For additional commands, e-mail: dev-help@cassandra.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org For additional commands, e-mail: dev-help@cassandra.apache.org