r 2019 07:08
> > To: dev@cassandra.apache.org
> > Subject: Re: [VOTE-2] Apache Cassandra Release Lifecycle
> >
> >
> > > We have discussed in the email thread[1] about Apache Cassandra
> > > Release Lifecycle. We came up with a doc[2] for it.
+1 nb
On Wed, Oct 9, 2019 at 11:00 PM Per Otterström
wrote:
> +1 nb
>
> -Original Message-
> From: Mick Semb Wever
> Sent: den 10 oktober 2019 07:08
> To: dev@cassandra.apache.org
> Subject: Re: [VOTE-2] Apache Cassandra Release Lifecycle
>
>
> >
+1 nb
-Original Message-
From: Mick Semb Wever
Sent: den 10 oktober 2019 07:08
To: dev@cassandra.apache.org
Subject: Re: [VOTE-2] Apache Cassandra Release Lifecycle
> We have discussed in the email thread[1] about Apache Cassandra
> Release Lifecycle. We came up with a
> We have discussed in the email thread[1] about Apache Cassandra Release
> Lifecycle. We came up with a doc[2] for it. We have finalized the doc
> here[3] Please vote on it if you agree with the content of the doc [3].
+1 nb
the doc is good. it adds value for users, and does not need to
+1, lets evolve the document as we gain more experience with the proposed
release lifecycle.
Dinesh
> On Oct 9, 2019, at 9:41 AM, Jon Haddad wrote:
>
> +1 works for me
>
> On Wed, Oct 9, 2019 at 9:30 AM Michael Shuler
> wrote:
>
>> +1
>>
>> --
>> Kind regards,
>> Michael
>>
>> On Wed,
+1
--
Kind regards,
Michael
On Wed, Oct 9, 2019 at 9:06 AM Aleksey Yeshchenko
wrote:
>
> +1 as a rather reasonable starting point; we can make changes to the process
> in the future if need be.
>
> > On 8 Oct 2019, at 19:00, sankalp kohli wrote:
> >
> > Hi,
> >We have discussed in the
+1 as a rather reasonable starting point; we can make changes to the process in
the future if need be.
> On 8 Oct 2019, at 19:00, 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. We have
keeping with our current
>>> convention.
>>>
>>>Re: "We should give users a way to plan, by having EOL dates"
>>>Incorporating EOL dates into our release management / planning is a
>>> great idea.
>>>
>>>Would you be willing t
d give users a way to plan, by having EOL dates"
>>>Incorporating EOL dates into our release management / planning is a
>>> great idea.
>>>
>>>Would you be willing to rephrase your comments in the form of
>> proposed
>>> edits to t
plan, by having EOL dates"
> > Incorporating EOL dates into our release management / planning is a
> > great idea.
> >
> > Would you be willing to rephrase your comments in the form of
> proposed
> > edits to the document?
> >
> > – Scott
> >
> >
gement / planning is a
> great idea.
>
> Would you be willing to rephrase your comments in the form of proposed
> edits to the document?
>
> – Scott
>
> ________________
> From: Stefan Podkowinski
> Sent: Tuesday, October 8, 2019 1:22 P
Would you be willing to rephrase your comments in the form of proposed
edits to the document?
– Scott
From: Stefan Podkowinski
Sent: Tuesday, October 8, 2019 1:22 PM
To: dev@cassandra.apache.org
Subject: Re: [VOTE-
ng is a great idea.
Would you be willing to rephrase your comments in the form of proposed edits to
the document?
– Scott
From: Stefan Podkowinski
Sent: Tuesday, October 8, 2019 1:22 PM
To: dev@cassandra.apache.org
Subject: Re: [VOTE-2] Apache Cassandra Release
From the document:
General Availability (GA): “A new branch is created for the release with
the new major version, limiting any new feature addition to the new
release branch, with new feature development will continue to happen
only on trunk.”
Maintenance: “Missing features from newer
+1
Don't have comment rights on the confluence article (or am too dense to
figure out _how_ to leave a comment). There's some stringency surrounding
clean CI + no flaky tests that I think bear further discussion; for what
it's worth I'm 100% in support of having hard gatekeeping so quality
+1 nb
From: sankalp kohli
Sent: Tuesday, October 8, 2019 11:00 AM
To: dev
Subject: [VOTE-2] 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. We
16 matches
Mail list logo
