Re: [VOTE] Release Apache Cassandra 2.1.21

[Michael Shuler]

I count 7 binding +1's, 1 non-binding +1 vote, and no others, so this
vote passes. I'll publish the artifacts as soon as I can.

Thanks for the discussion on support life of the 2.1 branch. I will not
be making any changes to the notes on the download page.

Kind regards,
Michael

On 2/2/19 6:32 PM, 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
> 




signature.asc
Description: OpenPGP digital signature

Re: [VOTE] Release Apache Cassandra 2.1.21

[Marcus Eriksson]

+1

Den ons 6 feb. 2019 kl 10:54 skrev Benedict Elliott Smith <
bened...@apache.org>:

> +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  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 
> > 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
>
>

Re: [VOTE] Release Apache Cassandra 2.1.21

[Benedict Elliott Smith]

+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  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 
> 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

Re: [VOTE] Release Apache Cassandra 2.1.21

[Jeff Jirsa]

+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 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
>
>

Re: [VOTE] Release Apache Cassandra 2.1.21

[Mick Semb Wever]

> 
> 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.
 - is there a reason we don't send out a pre-vote announcement that the 
artefacts are cut and can be tested? A number of apache projects do this and my 
impression is it provides a little patience in ensuring artefacts get tested 
before everyone rushes in to vote. We're not exactly offering anyone (users 
included) who is willing to test an artefact any time to do so.
 - we're not seeing/testing (or voting on) the sha256/512 checksums, as they're 
not uploaded until final release, as described in CASSANDRA-14970. 

regards,
Mick

-- 
https://issues.apache.org/jira/browse/MNG-5504

-
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org

Re: [VOTE] Release Apache Cassandra 2.1.21

[Stefan Podkowinski]

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-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org



--
Jon Haddad
http://www.rustyrazorblade.com
twitter: rustyrazorblade



-
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org



-
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: 

Re: [VOTE] Release Apache Cassandra 2.1.21

[Aleksey Yeshchenko]

Not sure we need another 2.1 release, this one included, but sure, +1

So long as the branch itself stays kinda open and most critical issues can have 
at least fixes for them committed, the interested parties can then keep 
building the artefacts manually.

Once 4.0 is out we can freeze the branch for good as well.

> On 3 Feb 2019, at 00: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-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org

Re: [VOTE] Release Apache Cassandra 2.1.21

[Anthony Grasso]

Hi Michael,

What you and Jon said makes sense.

You have addressed a follow up concern I had about making sure the site was
updated if we go ahead with making 2.1 EOL. I'm happy to help with site
changes if needed.

Cheers,
Anthony

On Mon, 4 Feb 2019 at 11: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-unsubscr...@cassandra.apache.org
>  For additional commands, e-mail: dev-h...@cassandra.apache.org
> 
> >>>
> >>> -
> >>> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> >>> For additional commands, e-mail: dev-h...@cassandra.apache.org
> >>>
> >>>
> >>
> >> --
> >> Jon Haddad
> >> http://www.rustyrazorblade.com
> >> twitter: rustyrazorblade
> >>
> >
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> For additional 

Re: [VOTE] Release Apache Cassandra 2.1.21

[Anthony Grasso]

+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-unsubscr...@cassandra.apache.org
> > > For additional commands, e-mail: dev-h...@cassandra.apache.org
> > >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> > For additional commands, e-mail: dev-h...@cassandra.apache.org
> >
> >
>
> --
> Jon Haddad
> http://www.rustyrazorblade.com
> twitter: rustyrazorblade
>

Re: [VOTE] Release Apache Cassandra 2.1.21

[Nate McCall]

+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-unsubscr...@cassandra.apache.org
> For additional commands, e-mail: dev-h...@cassandra.apache.org
>

-
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org

Re: [VOTE] Release Apache Cassandra 2.1.21

[Stefan Podkowinski]

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-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org

[VOTE] Release Apache Cassandra 2.1.21

[Michael Shuler]

*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



signature.asc
Description: OpenPGP digital signature