Re: [VOTE-2] Apache Cassandra Release Lifecycle

Indeed, sorry +1; we may need to tweak it going forward, but it's a great staring (or midway) point On 08/10/2019, 22:59, "Sankalp Kohli" wrote: Can we please stick to the vote here. We can always change the documentation as it will evolve over time. > On Oct 8, 2019, at

Re: [VOTE-2] Apache Cassandra Release Lifecycle

Can we please stick to the vote here. We can always change the documentation as it will evolve over time. > On Oct 8, 2019, at 2:57 PM, Joshua McKenzie wrote: > > It probably warrants a separate discussion about how we version. > > Also, robust +1 to what you said here bes and haddad ;) >

Re: [VOTE-2] Apache Cassandra Release Lifecycle

It probably warrants a separate discussion about how we version. Also, robust +1 to what you said here bes and haddad ;) On Tue, Oct 8, 2019 at 5:31 PM Jon Haddad wrote: > This has definitely been a confusing topic in the past, I completely agree > Benedict. Glad you brought this up. > > I'm

Re: [VOTE-2] Apache Cassandra Release Lifecycle

This has definitely been a confusing topic in the past, I completely agree Benedict. Glad you brought this up. I'm 100% on board with 5.0 after 4.0. On Tue, Oct 8, 2019 at 2:27 PM Benedict Elliott Smith wrote: > As a brief side-step on the topic only of versioning (which no doubt will > cause

Re: [VOTE-2] Apache Cassandra Release Lifecycle

As a brief side-step on the topic only of versioning (which no doubt will cause enough consternation), I personally endorse streamlining it. We have not had a consistently meaningful convention on this, at any point, and we made it even worse in the 3.x line. There's no real difference between

Re: [VOTE-2] Apache Cassandra Release Lifecycle

Re: "How can we decide that *all* new features are suppose to go into trunk only, if we don’t even have an idea about the upcoming release schedule?" This is a great question. My understanding of the intent of the document is that new features are generally expected to land in trunk, with an exc

Re: [VOTE-2] Apache Cassandra Release Lifecycle

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 generat

Re: Can we kick off a release?

I forgot to mention, we should also release alpha2 of 4.0. On Tue, Oct 8, 2019 at 1:04 PM Michael Shuler wrote: > Thanks Sam, I'm following #15193 and should catch the status change there. > > Michael > > On Tue, Oct 8, 2019 at 6:17 AM Sam Tunnicliffe wrote: > > > > CASSANDRA-15193 just got +1

Re: Can we kick off a release?

Thanks Sam, I'm following #15193 and should catch the status change there. Michael On Tue, Oct 8, 2019 at 6:17 AM Sam Tunnicliffe wrote: > > CASSANDRA-15193 just got +1’d yesterday and would be good to include in the > 3.0 and 3.11 releases. If you don’t mind holding off while I add a cqlsh tes

Re: [VOTE-2] Apache Cassandra Release Lifecycle

+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 doesn't

Re: [VOTE-2] Apache Cassandra Release Lifecycle

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

[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 have finalized the doc here[3] Please vote on it if you agree with the content of the doc [3]. We did not proceed with the previous vote as we want to use confluence for i

Re: [VOTE] Apache Cassandra Release Lifecycle

Thanks Sumanth. Let me start another vote On Tue, Oct 8, 2019 at 7:26 AM Sumanth Pasupuleti < sumanth.pasupuleti...@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/Rel

Re: [VOTE] Apache Cassandra Release Lifecycle

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

Re: Can we kick off a release?

CASSANDRA-15193 just got +1’d yesterday and would be good to include in the 3.0 and 3.11 releases. If you don’t mind holding off while I add a cqlsh test and merge it, that’d be good. Thanks, Sam > On 7 Oct 2019, at 22:54, Michael Shuler wrote: > > Will do! I probably won't get this done this