You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cassandra.apache.org by sankalp kohli <ko...@gmail.com> on 2019/09/30 18:51:30 UTC
[VOTE] Apache Cassandra Release Lifecycle
Hi,
We have discussed in the email thread[1] about Apache Cassandra Release
Lifecycle. We came up with a doc[2] for it. Please vote on it if you agree
with the content of the doc[2].
Thanks,
Sankalp
[1]
https://lists.apache.org/thread.html/c610b23f9002978636b66d09f0e0481ed3de9b78895050da22c91c6f@%3Cdev.cassandra.apache.org%3E
[2]
https://docs.google.com/document/d/1bS6sr-HSrHFjZb0welife6Qx7u3ZDgRiAoENMLYlfz8/edit#heading=h.633eppni91tw
Re: [VOTE] Apache Cassandra Release Lifecycle
Posted by sankalp kohli <ko...@gmail.com>.
Thanks Sumanth. Let me start another vote
On Tue, Oct 8, 2019 at 7:26 AM Sumanth Pasupuleti <
sumanth.pasupuleti.is@gmail.com> wrote:
> Thank you, Scott!
> I've moved the document content (along with outstanding comments) into
> cwiki at
> https://cwiki.apache.org/confluence/display/CASSANDRA/Release+Lifecycle.
> Made the GDoc deprecated and view-only, and left breadcrumbs to the cwiki
> in both the jira <https://issues.apache.org/jira/browse/CASSANDRA-15249>
> as
> well as the GDoc
> <
> https://docs.google.com/document/d/1bS6sr-HSrHFjZb0welife6Qx7u3ZDgRiAoENMLYlfz8/edit#
> >
> .
>
> On Mon, Oct 7, 2019 at 12:26 PM Jordan West <jo...@gmail.com> wrote:
>
> > +1 nb — to both the document and the benefits listed in Scott’s email.
> >
> > Jordan
> >
> > On Fri, Oct 4, 2019 at 2:26 PM Scott Andreas <sc...@paradoxica.net>
> wrote:
> >
> > > There are two main benefits to agreeing on this:
> > >
> > > 1. Providing clarity for contributors on release phases – i.e., what
> > types
> > > of changes are expected to land or be deferred during a particular
> point
> > in
> > > that cycle.
> > >
> > > 2. Providing semantic clarity to users of Cassandra in terms of what
> they
> > > can expect from a given release.
> > >
> > > The second one is more important. The document stands as a commitment
> > > between the Cassandra project and its users regarding what can be
> > expected
> > > from each type of release. It defines GA releases as "recommended for
> > > production deployment for all users," setting a standard of quality
> that
> > we
> > > aim to uphold together and that users can depend on. Affirming what it
> > > means for a release to be EOL, deprecated, or in maintenance signals
> > > importance of upgrading to a GA version.
> > >
> > > The prerelease phases set expectations for us as contributors to
> produce
> > a
> > > more stable release: what type of testing/validation is needed at what
> > > time, at which point interfaces/protocols solidify, when a release is
> > > considered feature complete, etc.
> > >
> > > Creating clarity for ourselves will help us build a better database,
> and
> > > creating clarity for our users will help give them the confidence to
> run
> > it.
> > >
> > > I want to thank Sumanth for his work on this document and to everyone
> > else
> > > who's contributed.
> > >
> > > I support it (+1 nb).
> > >
> > > – Scott
> > >
> > > ________________________________________
> > > From: Stefan Podkowinski <sp...@apache.org>
> > > Sent: Tuesday, October 1, 2019 1:43 PM
> > > To: dev@cassandra.apache.org
> > > Subject: Re: [VOTE] Apache Cassandra Release Lifecycle
> > >
> > > What exactly will be the implication of the outcome of this vote, in
> > > case the content is agreed upon? What's the proposal of the voting?
> > >
> > > The document seems to be informative rather then formal. It's verbose
> on
> > > definitions that should be commonly understood or can only broadly
> > > defined (what is alpha/beta/RC, GA for production, etc.), while at the
> > > same time is unclear and weasel-wordy on our actual commitment and
> rules.
> > >
> > >
> > > On 30.09.19 20:51, sankalp kohli wrote:
> > > > Hi,
> > > > We have discussed in the email thread[1] about Apache Cassandra
> > > Release
> > > > Lifecycle. We came up with a doc[2] for it. Please vote on it if you
> > > agree
> > > > with the content of the doc[2].
> > > >
> > > > Thanks,
> > > > Sankalp
> > > >
> > > > [1]
> > > >
> > >
> >
> https://lists.apache.org/thread.html/c610b23f9002978636b66d09f0e0481ed3de9b78895050da22c91c6f@%3Cdev.cassandra.apache.org%3E
> > > > [2]
> > > >
> > >
> >
> https://docs.google.com/document/d/1bS6sr-HSrHFjZb0welife6Qx7u3ZDgRiAoENMLYlfz8/edit#heading=h.633eppni91tw
> > > >
> > >
> > > ---------------------------------------------------------------------
> > > 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
> > >
> > >
> >
>
Re: [VOTE] Apache Cassandra Release Lifecycle
Posted by Sumanth Pasupuleti <su...@gmail.com>.
Thank you, Scott!
I've moved the document content (along with outstanding comments) into
cwiki at
https://cwiki.apache.org/confluence/display/CASSANDRA/Release+Lifecycle.
Made the GDoc deprecated and view-only, and left breadcrumbs to the cwiki
in both the jira <https://issues.apache.org/jira/browse/CASSANDRA-15249> as
well as the GDoc
<https://docs.google.com/document/d/1bS6sr-HSrHFjZb0welife6Qx7u3ZDgRiAoENMLYlfz8/edit#>
.
On Mon, Oct 7, 2019 at 12:26 PM Jordan West <jo...@gmail.com> wrote:
> +1 nb — to both the document and the benefits listed in Scott’s email.
>
> Jordan
>
> On Fri, Oct 4, 2019 at 2:26 PM Scott Andreas <sc...@paradoxica.net> wrote:
>
> > There are two main benefits to agreeing on this:
> >
> > 1. Providing clarity for contributors on release phases – i.e., what
> types
> > of changes are expected to land or be deferred during a particular point
> in
> > that cycle.
> >
> > 2. Providing semantic clarity to users of Cassandra in terms of what they
> > can expect from a given release.
> >
> > The second one is more important. The document stands as a commitment
> > between the Cassandra project and its users regarding what can be
> expected
> > from each type of release. It defines GA releases as "recommended for
> > production deployment for all users," setting a standard of quality that
> we
> > aim to uphold together and that users can depend on. Affirming what it
> > means for a release to be EOL, deprecated, or in maintenance signals
> > importance of upgrading to a GA version.
> >
> > The prerelease phases set expectations for us as contributors to produce
> a
> > more stable release: what type of testing/validation is needed at what
> > time, at which point interfaces/protocols solidify, when a release is
> > considered feature complete, etc.
> >
> > Creating clarity for ourselves will help us build a better database, and
> > creating clarity for our users will help give them the confidence to run
> it.
> >
> > I want to thank Sumanth for his work on this document and to everyone
> else
> > who's contributed.
> >
> > I support it (+1 nb).
> >
> > – Scott
> >
> > ________________________________________
> > From: Stefan Podkowinski <sp...@apache.org>
> > Sent: Tuesday, October 1, 2019 1:43 PM
> > To: dev@cassandra.apache.org
> > Subject: Re: [VOTE] Apache Cassandra Release Lifecycle
> >
> > What exactly will be the implication of the outcome of this vote, in
> > case the content is agreed upon? What's the proposal of the voting?
> >
> > The document seems to be informative rather then formal. It's verbose on
> > definitions that should be commonly understood or can only broadly
> > defined (what is alpha/beta/RC, GA for production, etc.), while at the
> > same time is unclear and weasel-wordy on our actual commitment and rules.
> >
> >
> > On 30.09.19 20:51, sankalp kohli wrote:
> > > Hi,
> > > We have discussed in the email thread[1] about Apache Cassandra
> > Release
> > > Lifecycle. We came up with a doc[2] for it. Please vote on it if you
> > agree
> > > with the content of the doc[2].
> > >
> > > Thanks,
> > > Sankalp
> > >
> > > [1]
> > >
> >
> https://lists.apache.org/thread.html/c610b23f9002978636b66d09f0e0481ed3de9b78895050da22c91c6f@%3Cdev.cassandra.apache.org%3E
> > > [2]
> > >
> >
> https://docs.google.com/document/d/1bS6sr-HSrHFjZb0welife6Qx7u3ZDgRiAoENMLYlfz8/edit#heading=h.633eppni91tw
> > >
> >
> > ---------------------------------------------------------------------
> > 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
> >
> >
>
Re: [VOTE] Apache Cassandra Release Lifecycle
Posted by Jordan West <jo...@gmail.com>.
+1 nb — to both the document and the benefits listed in Scott’s email.
Jordan
On Fri, Oct 4, 2019 at 2:26 PM Scott Andreas <sc...@paradoxica.net> wrote:
> There are two main benefits to agreeing on this:
>
> 1. Providing clarity for contributors on release phases – i.e., what types
> of changes are expected to land or be deferred during a particular point in
> that cycle.
>
> 2. Providing semantic clarity to users of Cassandra in terms of what they
> can expect from a given release.
>
> The second one is more important. The document stands as a commitment
> between the Cassandra project and its users regarding what can be expected
> from each type of release. It defines GA releases as "recommended for
> production deployment for all users," setting a standard of quality that we
> aim to uphold together and that users can depend on. Affirming what it
> means for a release to be EOL, deprecated, or in maintenance signals
> importance of upgrading to a GA version.
>
> The prerelease phases set expectations for us as contributors to produce a
> more stable release: what type of testing/validation is needed at what
> time, at which point interfaces/protocols solidify, when a release is
> considered feature complete, etc.
>
> Creating clarity for ourselves will help us build a better database, and
> creating clarity for our users will help give them the confidence to run it.
>
> I want to thank Sumanth for his work on this document and to everyone else
> who's contributed.
>
> I support it (+1 nb).
>
> – Scott
>
> ________________________________________
> From: Stefan Podkowinski <sp...@apache.org>
> Sent: Tuesday, October 1, 2019 1:43 PM
> To: dev@cassandra.apache.org
> Subject: Re: [VOTE] Apache Cassandra Release Lifecycle
>
> What exactly will be the implication of the outcome of this vote, in
> case the content is agreed upon? What's the proposal of the voting?
>
> The document seems to be informative rather then formal. It's verbose on
> definitions that should be commonly understood or can only broadly
> defined (what is alpha/beta/RC, GA for production, etc.), while at the
> same time is unclear and weasel-wordy on our actual commitment and rules.
>
>
> On 30.09.19 20:51, sankalp kohli wrote:
> > Hi,
> > We have discussed in the email thread[1] about Apache Cassandra
> Release
> > Lifecycle. We came up with a doc[2] for it. Please vote on it if you
> agree
> > with the content of the doc[2].
> >
> > Thanks,
> > Sankalp
> >
> > [1]
> >
> https://lists.apache.org/thread.html/c610b23f9002978636b66d09f0e0481ed3de9b78895050da22c91c6f@%3Cdev.cassandra.apache.org%3E
> > [2]
> >
> https://docs.google.com/document/d/1bS6sr-HSrHFjZb0welife6Qx7u3ZDgRiAoENMLYlfz8/edit#heading=h.633eppni91tw
> >
>
> ---------------------------------------------------------------------
> 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
>
>
Re: [VOTE] Apache Cassandra Release Lifecycle
Posted by Scott Andreas <sc...@paradoxica.net>.
There are two main benefits to agreeing on this:
1. Providing clarity for contributors on release phases – i.e., what types of changes are expected to land or be deferred during a particular point in that cycle.
2. Providing semantic clarity to users of Cassandra in terms of what they can expect from a given release.
The second one is more important. The document stands as a commitment between the Cassandra project and its users regarding what can be expected from each type of release. It defines GA releases as "recommended for production deployment for all users," setting a standard of quality that we aim to uphold together and that users can depend on. Affirming what it means for a release to be EOL, deprecated, or in maintenance signals importance of upgrading to a GA version.
The prerelease phases set expectations for us as contributors to produce a more stable release: what type of testing/validation is needed at what time, at which point interfaces/protocols solidify, when a release is considered feature complete, etc.
Creating clarity for ourselves will help us build a better database, and creating clarity for our users will help give them the confidence to run it.
I want to thank Sumanth for his work on this document and to everyone else who's contributed.
I support it (+1 nb).
– Scott
________________________________________
From: Stefan Podkowinski <sp...@apache.org>
Sent: Tuesday, October 1, 2019 1:43 PM
To: dev@cassandra.apache.org
Subject: Re: [VOTE] Apache Cassandra Release Lifecycle
What exactly will be the implication of the outcome of this vote, in
case the content is agreed upon? What's the proposal of the voting?
The document seems to be informative rather then formal. It's verbose on
definitions that should be commonly understood or can only broadly
defined (what is alpha/beta/RC, GA for production, etc.), while at the
same time is unclear and weasel-wordy on our actual commitment and rules.
On 30.09.19 20:51, sankalp kohli wrote:
> Hi,
> We have discussed in the email thread[1] about Apache Cassandra Release
> Lifecycle. We came up with a doc[2] for it. Please vote on it if you agree
> with the content of the doc[2].
>
> Thanks,
> Sankalp
>
> [1]
> https://lists.apache.org/thread.html/c610b23f9002978636b66d09f0e0481ed3de9b78895050da22c91c6f@%3Cdev.cassandra.apache.org%3E
> [2]
> https://docs.google.com/document/d/1bS6sr-HSrHFjZb0welife6Qx7u3ZDgRiAoENMLYlfz8/edit#heading=h.633eppni91tw
>
---------------------------------------------------------------------
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
Re: [VOTE] Apache Cassandra Release Lifecycle
Posted by Stefan Podkowinski <sp...@apache.org>.
What exactly will be the implication of the outcome of this vote, in
case the content is agreed upon? What's the proposal of the voting?
The document seems to be informative rather then formal. It's verbose on
definitions that should be commonly understood or can only broadly
defined (what is alpha/beta/RC, GA for production, etc.), while at the
same time is unclear and weasel-wordy on our actual commitment and rules.
On 30.09.19 20:51, sankalp kohli wrote:
> Hi,
> We have discussed in the email thread[1] about Apache Cassandra Release
> Lifecycle. We came up with a doc[2] for it. Please vote on it if you agree
> with the content of the doc[2].
>
> Thanks,
> Sankalp
>
> [1]
> https://lists.apache.org/thread.html/c610b23f9002978636b66d09f0e0481ed3de9b78895050da22c91c6f@%3Cdev.cassandra.apache.org%3E
> [2]
> https://docs.google.com/document/d/1bS6sr-HSrHFjZb0welife6Qx7u3ZDgRiAoENMLYlfz8/edit#heading=h.633eppni91tw
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
For additional commands, e-mail: dev-help@cassandra.apache.org
Re: [VOTE] Apache Cassandra Release Lifecycle
Posted by Sumanth Pasupuleti <su...@gmail.com>.
I made a couple of additional changes to the document based on the
comments, and there are a couple more that need to be addressed.
I will work on moving this document to cwiki.
Thanks,
Sumanth
On Tue, Oct 1, 2019 at 10:02 AM Dinesh Joshi <dj...@apache.org> wrote:
> There are a few points that need to be clarified in doc. I am also fine if
> we want to adopt the document as-is and then refine it as we build
> experience with the process.
>
> Dinesh
>
> > On Sep 30, 2019, at 3:24 PM, sankalp kohli <ko...@gmail.com>
> wrote:
> >
> > Sure..lets do that.
> >
> > On Mon, Sep 30, 2019 at 3:21 PM Benedict Elliott Smith <
> benedict@apache.org>
> > wrote:
> >
> >> Perhaps we should move the proposed document to the cwiki for purposes
> of
> >> voting? That way it's in a place owned by the project, with a permanent
> >> history. Otherwise it's not entirely clear what was voted on.
> >>
> >>
> >> On 30/09/2019, 20:10, "Sumanth Pasupuleti" <
> >> sumanth.pasupuleti.is@gmail.com> wrote:
> >>
> >> +1
> >>
> >> On Mon, Sep 30, 2019 at 12:00 PM Nate McCall <zz...@gmail.com>
> >> wrote:
> >>
> >>> +1
> >>>
> >>> On Tue, Oct 1, 2019 at 7:52 AM sankalp kohli <kohlisankalp@gmail.com
> >>>
> >>> wrote:
> >>>
> >>>> Hi,
> >>>> We have discussed in the email thread[1] about Apache Cassandra
> >>> Release
> >>>> Lifecycle. We came up with a doc[2] for it. Please vote on it if
> >> you
> >>> agree
> >>>> with the content of the doc[2].
> >>>>
> >>>> Thanks,
> >>>> Sankalp
> >>>>
> >>>> [1]
> >>>>
> >>>>
> >>>
> >>
> https://lists.apache.org/thread.html/c610b23f9002978636b66d09f0e0481ed3de9b78895050da22c91c6f@%3Cdev.cassandra.apache.org%3E
> >>>> [2]
> >>>>
> >>>>
> >>>
> >>
> https://docs.google.com/document/d/1bS6sr-HSrHFjZb0welife6Qx7u3ZDgRiAoENMLYlfz8/edit#heading=h.633eppni91tw
> >>>>
> >>>
> >>
> >>
> >>
> >>
> >> ---------------------------------------------------------------------
> >> 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
>
>
Re: [VOTE] Apache Cassandra Release Lifecycle
Posted by Dinesh Joshi <dj...@apache.org>.
There are a few points that need to be clarified in doc. I am also fine if we want to adopt the document as-is and then refine it as we build experience with the process.
Dinesh
> On Sep 30, 2019, at 3:24 PM, sankalp kohli <ko...@gmail.com> wrote:
>
> Sure..lets do that.
>
> On Mon, Sep 30, 2019 at 3:21 PM Benedict Elliott Smith <be...@apache.org>
> wrote:
>
>> Perhaps we should move the proposed document to the cwiki for purposes of
>> voting? That way it's in a place owned by the project, with a permanent
>> history. Otherwise it's not entirely clear what was voted on.
>>
>>
>> On 30/09/2019, 20:10, "Sumanth Pasupuleti" <
>> sumanth.pasupuleti.is@gmail.com> wrote:
>>
>> +1
>>
>> On Mon, Sep 30, 2019 at 12:00 PM Nate McCall <zz...@gmail.com>
>> wrote:
>>
>>> +1
>>>
>>> On Tue, Oct 1, 2019 at 7:52 AM sankalp kohli <kohlisankalp@gmail.com
>>>
>>> wrote:
>>>
>>>> Hi,
>>>> We have discussed in the email thread[1] about Apache Cassandra
>>> Release
>>>> Lifecycle. We came up with a doc[2] for it. Please vote on it if
>> you
>>> agree
>>>> with the content of the doc[2].
>>>>
>>>> Thanks,
>>>> Sankalp
>>>>
>>>> [1]
>>>>
>>>>
>>>
>> https://lists.apache.org/thread.html/c610b23f9002978636b66d09f0e0481ed3de9b78895050da22c91c6f@%3Cdev.cassandra.apache.org%3E
>>>> [2]
>>>>
>>>>
>>>
>> https://docs.google.com/document/d/1bS6sr-HSrHFjZb0welife6Qx7u3ZDgRiAoENMLYlfz8/edit#heading=h.633eppni91tw
>>>>
>>>
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> 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
Re: [VOTE] Apache Cassandra Release Lifecycle
Posted by sankalp kohli <ko...@gmail.com>.
Sure..lets do that.
On Mon, Sep 30, 2019 at 3:21 PM Benedict Elliott Smith <be...@apache.org>
wrote:
> Perhaps we should move the proposed document to the cwiki for purposes of
> voting? That way it's in a place owned by the project, with a permanent
> history. Otherwise it's not entirely clear what was voted on.
>
>
> On 30/09/2019, 20:10, "Sumanth Pasupuleti" <
> sumanth.pasupuleti.is@gmail.com> wrote:
>
> +1
>
> On Mon, Sep 30, 2019 at 12:00 PM Nate McCall <zz...@gmail.com>
> wrote:
>
> > +1
> >
> > On Tue, Oct 1, 2019 at 7:52 AM sankalp kohli <kohlisankalp@gmail.com
> >
> > wrote:
> >
> > > Hi,
> > > We have discussed in the email thread[1] about Apache Cassandra
> > Release
> > > Lifecycle. We came up with a doc[2] for it. Please vote on it if
> you
> > agree
> > > with the content of the doc[2].
> > >
> > > Thanks,
> > > Sankalp
> > >
> > > [1]
> > >
> > >
> >
> https://lists.apache.org/thread.html/c610b23f9002978636b66d09f0e0481ed3de9b78895050da22c91c6f@%3Cdev.cassandra.apache.org%3E
> > > [2]
> > >
> > >
> >
> https://docs.google.com/document/d/1bS6sr-HSrHFjZb0welife6Qx7u3ZDgRiAoENMLYlfz8/edit#heading=h.633eppni91tw
> > >
> >
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
> For additional commands, e-mail: dev-help@cassandra.apache.org
>
>
Re: [VOTE] Apache Cassandra Release Lifecycle
Posted by Benedict Elliott Smith <be...@apache.org>.
Perhaps we should move the proposed document to the cwiki for purposes of voting? That way it's in a place owned by the project, with a permanent history. Otherwise it's not entirely clear what was voted on.
On 30/09/2019, 20:10, "Sumanth Pasupuleti" <su...@gmail.com> wrote:
+1
On Mon, Sep 30, 2019 at 12:00 PM Nate McCall <zz...@gmail.com> wrote:
> +1
>
> On Tue, Oct 1, 2019 at 7:52 AM sankalp kohli <ko...@gmail.com>
> wrote:
>
> > Hi,
> > We have discussed in the email thread[1] about Apache Cassandra
> Release
> > Lifecycle. We came up with a doc[2] for it. Please vote on it if you
> agree
> > with the content of the doc[2].
> >
> > Thanks,
> > Sankalp
> >
> > [1]
> >
> >
> https://lists.apache.org/thread.html/c610b23f9002978636b66d09f0e0481ed3de9b78895050da22c91c6f@%3Cdev.cassandra.apache.org%3E
> > [2]
> >
> >
> https://docs.google.com/document/d/1bS6sr-HSrHFjZb0welife6Qx7u3ZDgRiAoENMLYlfz8/edit#heading=h.633eppni91tw
> >
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
For additional commands, e-mail: dev-help@cassandra.apache.org
Re: [VOTE] Apache Cassandra Release Lifecycle
Posted by sankalp kohli <ko...@gmail.com>.
Vote will be open for 72 hours.
On Mon, Sep 30, 2019 at 12:09 PM Sumanth Pasupuleti <
sumanth.pasupuleti.is@gmail.com> wrote:
> +1
>
> On Mon, Sep 30, 2019 at 12:00 PM Nate McCall <zz...@gmail.com> wrote:
>
> > +1
> >
> > On Tue, Oct 1, 2019 at 7:52 AM sankalp kohli <ko...@gmail.com>
> > wrote:
> >
> > > Hi,
> > > We have discussed in the email thread[1] about Apache Cassandra
> > Release
> > > Lifecycle. We came up with a doc[2] for it. Please vote on it if you
> > agree
> > > with the content of the doc[2].
> > >
> > > Thanks,
> > > Sankalp
> > >
> > > [1]
> > >
> > >
> >
> https://lists.apache.org/thread.html/c610b23f9002978636b66d09f0e0481ed3de9b78895050da22c91c6f@%3Cdev.cassandra.apache.org%3E
> > > [2]
> > >
> > >
> >
> https://docs.google.com/document/d/1bS6sr-HSrHFjZb0welife6Qx7u3ZDgRiAoENMLYlfz8/edit#heading=h.633eppni91tw
> > >
> >
>
Re: [VOTE] Apache Cassandra Release Lifecycle
Posted by Sumanth Pasupuleti <su...@gmail.com>.
+1
On Mon, Sep 30, 2019 at 12:00 PM Nate McCall <zz...@gmail.com> wrote:
> +1
>
> On Tue, Oct 1, 2019 at 7:52 AM sankalp kohli <ko...@gmail.com>
> wrote:
>
> > Hi,
> > We have discussed in the email thread[1] about Apache Cassandra
> Release
> > Lifecycle. We came up with a doc[2] for it. Please vote on it if you
> agree
> > with the content of the doc[2].
> >
> > Thanks,
> > Sankalp
> >
> > [1]
> >
> >
> https://lists.apache.org/thread.html/c610b23f9002978636b66d09f0e0481ed3de9b78895050da22c91c6f@%3Cdev.cassandra.apache.org%3E
> > [2]
> >
> >
> https://docs.google.com/document/d/1bS6sr-HSrHFjZb0welife6Qx7u3ZDgRiAoENMLYlfz8/edit#heading=h.633eppni91tw
> >
>
Re: [VOTE] Apache Cassandra Release Lifecycle
Posted by Nate McCall <zz...@gmail.com>.
+1
On Tue, Oct 1, 2019 at 7:52 AM sankalp kohli <ko...@gmail.com> wrote:
> Hi,
> We have discussed in the email thread[1] about Apache Cassandra Release
> Lifecycle. We came up with a doc[2] for it. Please vote on it if you agree
> with the content of the doc[2].
>
> Thanks,
> Sankalp
>
> [1]
>
> https://lists.apache.org/thread.html/c610b23f9002978636b66d09f0e0481ed3de9b78895050da22c91c6f@%3Cdev.cassandra.apache.org%3E
> [2]
>
> https://docs.google.com/document/d/1bS6sr-HSrHFjZb0welife6Qx7u3ZDgRiAoENMLYlfz8/edit#heading=h.633eppni91tw
>