Re: Coordinator Write Metrics per CF
It would be good to have it. Its not that its not there because its difficult or anything. I think its more that the read latency metric was needed for speculative retry so it was added but the write side wasn't needed for that feature so wasn't added at same time. It would be very useful in determining the table that the coordinator writes are slow to. Chris > On Feb 11, 2018, at 10:33 PM, kurt greaves wrote: > > I've tried to search around for a reason for this in the past and haven't > found one. I don't think it's a bad idea. Would be a helpful metric to > diagnose internode networking issues - although I'll note that the read > metric will also achieve this assuming you have enough reads to get some > useful information out of it. > > On 9 February 2018 at 17:43, Sumanth Pasupuleti < > sumanth.pasupuleti...@gmail.com> wrote: > >> There is an existing CoordinatorReadLatency table metric. I am looking to >> add CoordinatorWriteLatency table metric - however, before I attempt a shot >> at it, would like to know if anyone has context around why we currently do >> not have such metric (while we have the read metric) - if someone has >> already attempted and realized its a bad idea for some reason. >> >> Thanks, >> Sumanth >> - 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.20
I propose the following artifacts for release as 2.1.20. sha1: b2949439ec62077128103540e42570238520f4ee Git: http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.1.20-tentative Artifacts: https://repository.apache.org/content/repositories/orgapachecassandra-1152/org/apache/cassandra/apache-cassandra/2.1.20/ Staging repository: https://repository.apache.org/content/repositories/orgapachecassandra-1152/ Debian and RPM packages are available here: http://people.apache.org/~mshuler *** This release addresses an important fix for CASSANDRA-14092 *** "Max ttl of 20 years will overflow localDeletionTime" https://issues.apache.org/jira/browse/CASSANDRA-14092 The vote will be open for 72 hours (longer if needed). [1]: (CHANGES.txt) https://goo.gl/5i2nw9 [2]: (NEWS.txt) https://goo.gl/i9Fg2u signature.asc Description: OpenPGP digital signature
[VOTE] Release Apache Cassandra 2.2.12
I propose the following artifacts for release as 2.2.12. sha1: 1602e606348959aead18531cb8027afb15f276e7 Git: http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.2.12-tentative Artifacts: https://repository.apache.org/content/repositories/orgapachecassandra-1153/org/apache/cassandra/apache-cassandra/2.2.12/ Staging repository: https://repository.apache.org/content/repositories/orgapachecassandra-1153/ Debian and RPM packages are available here: http://people.apache.org/~mshuler *** This release addresses an important fix for CASSANDRA-14092 *** "Max ttl of 20 years will overflow localDeletionTime" https://issues.apache.org/jira/browse/CASSANDRA-14092 The vote will be open for 72 hours (longer if needed). [1]: (CHANGES.txt) https://goo.gl/QkJeXH [2]: (NEWS.txt) https://goo.gl/A4iKFb signature.asc Description: OpenPGP digital signature
[VOTE] Release Apache Cassandra 3.0.16
I propose the following artifacts for release as 3.0.16. sha1: 91e83c72de109521074b14a8eeae1309c3b1f215 Git: http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.16-tentative Artifacts: https://repository.apache.org/content/repositories/orgapachecassandra-1154/org/apache/cassandra/apache-cassandra/3.0.16/ Staging repository: https://repository.apache.org/content/repositories/orgapachecassandra-1154/ Debian and RPM packages are available here: http://people.apache.org/~mshuler *** This release addresses an important fix for CASSANDRA-14092 *** "Max ttl of 20 years will overflow localDeletionTime" https://issues.apache.org/jira/browse/CASSANDRA-14092 The vote will be open for 72 hours (longer if needed). [1]: (CHANGES.txt) https://goo.gl/rLj59Z [2]: (NEWS.txt) https://goo.gl/EkrT4G signature.asc Description: OpenPGP digital signature
[VOTE] Release Apache Cassandra 3.11.2
I propose the following artifacts for release as 3.11.2. sha1: f6ec5c5d18c2900af0ef6e314edbd19aaa682a55 Git: http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.11.2-tentative Artifacts: https://repository.apache.org/content/repositories/orgapachecassandra-1155/org/apache/cassandra/apache-cassandra/3.11.2/ Staging repository: https://repository.apache.org/content/repositories/orgapachecassandra-1155/ Debian and RPM packages are available here: http://people.apache.org/~mshuler *** This release addresses an important fix for CASSANDRA-14092 *** "Max ttl of 20 years will overflow localDeletionTime" https://issues.apache.org/jira/browse/CASSANDRA-14092 The vote will be open for 72 hours (longer if needed). [1]: (CHANGES.txt) https://goo.gl/RLZLrR [2]: (NEWS.txt) https://goo.gl/kpnVHp signature.asc Description: OpenPGP digital signature
Re: [VOTE] Release Apache Cassandra 2.1.20
+1 > On Feb 12, 2018, at 12:30 PM, Michael Shuler wrote: > > I propose the following artifacts for release as 2.1.20. > > sha1: b2949439ec62077128103540e42570238520f4ee > Git: > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.1.20-tentative > Artifacts: > https://repository.apache.org/content/repositories/orgapachecassandra-1152/org/apache/cassandra/apache-cassandra/2.1.20/ > Staging repository: > https://repository.apache.org/content/repositories/orgapachecassandra-1152/ > > Debian and RPM packages are available here: > http://people.apache.org/~mshuler > > *** This release addresses an important fix for CASSANDRA-14092 *** >"Max ttl of 20 years will overflow localDeletionTime" >https://issues.apache.org/jira/browse/CASSANDRA-14092 > > The vote will be open for 72 hours (longer if needed). > > [1]: (CHANGES.txt) https://goo.gl/5i2nw9 > [2]: (NEWS.txt) https://goo.gl/i9Fg2u > - 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.2.12
> I propose the following artifacts for release as 2.2.12. +1 - To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org
Re: [VOTE] Release Apache Cassandra 3.0.16
> I propose the following artifacts for release as 3.0.16. > +1 - To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org
Re: [VOTE] Release Apache Cassandra 3.11.2
> I propose the following artifacts for release as 3.11.2. > +1 - 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.20
> I propose the following artifacts for release as 2.1.20. > +1 - 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.2.12
+1 On Mon, Feb 12, 2018 at 2:30 PM, Michael Shuler wrote: > I propose the following artifacts for release as 2.2.12. > > sha1: 1602e606348959aead18531cb8027afb15f276e7 > Git: > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a= > shortlog;h=refs/tags/2.2.12-tentative > Artifacts: > https://repository.apache.org/content/repositories/ > orgapachecassandra-1153/org/apache/cassandra/apache-cassandra/2.2.12/ > Staging repository: > https://repository.apache.org/content/repositories/ > orgapachecassandra-1153/ > > Debian and RPM packages are available here: > http://people.apache.org/~mshuler > > *** This release addresses an important fix for CASSANDRA-14092 *** > "Max ttl of 20 years will overflow localDeletionTime" > https://issues.apache.org/jira/browse/CASSANDRA-14092 > > The vote will be open for 72 hours (longer if needed). > > [1]: (CHANGES.txt) https://goo.gl/QkJeXH > [2]: (NEWS.txt) https://goo.gl/A4iKFb > >
Re: [VOTE] Release Apache Cassandra 2.1.20
+1 On Mon, Feb 12, 2018 at 2:30 PM, Michael Shuler wrote: > I propose the following artifacts for release as 2.1.20. > > sha1: b2949439ec62077128103540e42570238520f4ee > Git: > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a= > shortlog;h=refs/tags/2.1.20-tentative > Artifacts: > https://repository.apache.org/content/repositories/ > orgapachecassandra-1152/org/apache/cassandra/apache-cassandra/2.1.20/ > Staging repository: > https://repository.apache.org/content/repositories/ > orgapachecassandra-1152/ > > Debian and RPM packages are available here: > http://people.apache.org/~mshuler > > *** This release addresses an important fix for CASSANDRA-14092 *** > "Max ttl of 20 years will overflow localDeletionTime" > https://issues.apache.org/jira/browse/CASSANDRA-14092 > > The vote will be open for 72 hours (longer if needed). > > [1]: (CHANGES.txt) https://goo.gl/5i2nw9 > [2]: (NEWS.txt) https://goo.gl/i9Fg2u > >
Re: [VOTE] Release Apache Cassandra 3.11.2
+1 On Mon, Feb 12, 2018 at 2:31 PM, Michael Shuler wrote: > I propose the following artifacts for release as 3.11.2. > > sha1: f6ec5c5d18c2900af0ef6e314edbd19aaa682a55 > Git: > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a= > shortlog;h=refs/tags/3.11.2-tentative > Artifacts: > https://repository.apache.org/content/repositories/ > orgapachecassandra-1155/org/apache/cassandra/apache-cassandra/3.11.2/ > Staging repository: > https://repository.apache.org/content/repositories/ > orgapachecassandra-1155/ > > Debian and RPM packages are available here: > http://people.apache.org/~mshuler > > *** This release addresses an important fix for CASSANDRA-14092 *** > "Max ttl of 20 years will overflow localDeletionTime" > https://issues.apache.org/jira/browse/CASSANDRA-14092 > > The vote will be open for 72 hours (longer if needed). > > [1]: (CHANGES.txt) https://goo.gl/RLZLrR > [2]: (NEWS.txt) https://goo.gl/kpnVHp > >
Re: [VOTE] Release Apache Cassandra 3.0.16
+1 On Mon, Feb 12, 2018 at 2:31 PM, Michael Shuler wrote: > I propose the following artifacts for release as 3.0.16. > > sha1: 91e83c72de109521074b14a8eeae1309c3b1f215 > Git: > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a= > shortlog;h=refs/tags/3.0.16-tentative > Artifacts: > https://repository.apache.org/content/repositories/ > orgapachecassandra-1154/org/apache/cassandra/apache-cassandra/3.0.16/ > Staging repository: > https://repository.apache.org/content/repositories/ > orgapachecassandra-1154/ > > Debian and RPM packages are available here: > http://people.apache.org/~mshuler > > *** This release addresses an important fix for CASSANDRA-14092 *** > "Max ttl of 20 years will overflow localDeletionTime" > https://issues.apache.org/jira/browse/CASSANDRA-14092 > > The vote will be open for 72 hours (longer if needed). > > [1]: (CHANGES.txt) https://goo.gl/rLj59Z > [2]: (NEWS.txt) https://goo.gl/EkrT4G > >
Re: [VOTE] Release Apache Cassandra 3.11.2
> I propose the following artifacts for release as 3.11.2. > … > The vote will be open for 72 hours (longer if needed). I just pushed the back-port of CASSANDRA-13080 (under CASSANDRA-14212). This is the improvement "Use new token allocation for non bootstrap case as well". We've seen that this effects 3.11.1 users and that it would be positive to see it in 3.11.2. Any chance we could recut 3.11.2 ? regards, Mick - To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org
Re: [VOTE] Release Apache Cassandra 3.11.2
I’m a +1 on getting this into 3.11.2. > On Feb 12, 2018, at 1:11 PM, mck wrote: > >> I propose the following artifacts for release as 3.11.2. >> … >> The vote will be open for 72 hours (longer if needed). > > > I just pushed the back-port of CASSANDRA-13080 (under CASSANDRA-14212). > This is the improvement "Use new token allocation for non bootstrap case as > well". > We've seen that this effects 3.11.1 users and that it would be positive to > see it in 3.11.2. > > Any chance we could recut 3.11.2 ? > > regards, > Mick > > - > 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 3.11.2
I thought we had committed CASSANDRA-14212 last week. We need a release bad enough that I don't want to sink this with a -1, but we have seen this be an issue with folks a couple of times recently. On Tue, Feb 13, 2018 at 10:16 AM, Jon Haddad wrote: > I’m a +1 on getting this into 3.11.2. > >> On Feb 12, 2018, at 1:11 PM, mck wrote: >> >>> I propose the following artifacts for release as 3.11.2. >>> … >>> The vote will be open for 72 hours (longer if needed). >> >> >> I just pushed the back-port of CASSANDRA-13080 (under CASSANDRA-14212). >> This is the improvement "Use new token allocation for non bootstrap case as >> well". >> We've seen that this effects 3.11.1 users and that it would be positive to >> see it in 3.11.2. >> >> Any chance we could recut 3.11.2 ? >> >> regards, >> Mick >> >> - >> 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 > - To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org
Re: [VOTE] Release Apache Cassandra 3.11.2
May as well just recut and include it IMO. Sure, the issue is work-aroundable, but in a pretty terrible way. Only a few hours will be lost (sorry Michael :/)
[VOTE VETOED] Release Apache Cassandra 3.11.2
On 02/12/2018 04:53 PM, kurt greaves wrote: > May as well just recut and include it IMO. Sure, the issue is > work-aroundable, but in a pretty terrible way. Only a few hours will be > lost (sorry Michael :/) Veto by myself, based on the previous comments. I've deleted the 3.11.2-tentative pointing to sha f6ec5c5 and will roll up another set of artifacts at sha 8a5e88f. Take 2 vote on the way. Thanks all! Michael - To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org
[VOTE] (Take 2) Release Apache Cassandra 3.11.2
I propose the following artifacts for release as 3.11.2. sha1: 8a5e88f635fdb984505a99a553b5799cedccd06d Git: http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.11.2-tentative Artifacts: https://repository.apache.org/content/repositories/orgapachecassandra-1156/org/apache/cassandra/apache-cassandra/3.11.2/ Staging repository: https://repository.apache.org/content/repositories/orgapachecassandra-1156/ Debian and RPM packages are available here: http://people.apache.org/~mshuler *** This release addresses an important fix for CASSANDRA-14092 *** "Max ttl of 20 years will overflow localDeletionTime" https://issues.apache.org/jira/browse/CASSANDRA-14092 The vote will be open for 72 hours (longer if needed). [1]: (CHANGES.txt) https://goo.gl/RLZLrR [2]: (NEWS.txt) https://goo.gl/kpnVHp signature.asc Description: OpenPGP digital signature
Re: [VOTE] (Take 2) Release Apache Cassandra 3.11.2
+1 Thanks for the reroll!! On Feb 13, 2018 4:41 PM, "Michael Shuler" wrote: > I propose the following artifacts for release as 3.11.2. > > sha1: 8a5e88f635fdb984505a99a553b5799cedccd06d > Git: > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a= > shortlog;h=refs/tags/3.11.2-tentative > Artifacts: > https://repository.apache.org/content/repositories/ > orgapachecassandra-1156/org/apache/cassandra/apache-cassandra/3.11.2/ > Staging repository: > https://repository.apache.org/content/repositories/ > orgapachecassandra-1156/ > > Debian and RPM packages are available here: > http://people.apache.org/~mshuler > > *** This release addresses an important fix for CASSANDRA-14092 *** > "Max ttl of 20 years will overflow localDeletionTime" > https://issues.apache.org/jira/browse/CASSANDRA-14092 > > The vote will be open for 72 hours (longer if needed). > > [1]: (CHANGES.txt) https://goo.gl/RLZLrR > [2]: (NEWS.txt) https://goo.gl/kpnVHp > >
Re: [VOTE] Release Apache Cassandra 3.0.16
+1 On Mon, Feb 12, 2018 at 1:03 PM, Brandon Williams wrote: > +1 > > On Mon, Feb 12, 2018 at 2:31 PM, Michael Shuler > wrote: > > > I propose the following artifacts for release as 3.0.16. > > > > sha1: 91e83c72de109521074b14a8eeae1309c3b1f215 > > Git: > > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a= > > shortlog;h=refs/tags/3.0.16-tentative > > Artifacts: > > https://repository.apache.org/content/repositories/ > > orgapachecassandra-1154/org/apache/cassandra/apache-cassandra/3.0.16/ > > Staging repository: > > https://repository.apache.org/content/repositories/ > > orgapachecassandra-1154/ > > > > Debian and RPM packages are available here: > > http://people.apache.org/~mshuler > > > > *** This release addresses an important fix for CASSANDRA-14092 *** > > "Max ttl of 20 years will overflow localDeletionTime" > > https://issues.apache.org/jira/browse/CASSANDRA-14092 > > > > The vote will be open for 72 hours (longer if needed). > > > > [1]: (CHANGES.txt) https://goo.gl/rLj59Z > > [2]: (NEWS.txt) https://goo.gl/EkrT4G > > > > >
Re: [VOTE] (Take 2) Release Apache Cassandra 3.11.2
+1 On Mon, Feb 12, 2018 at 7:40 PM, Michael Shuler wrote: > I propose the following artifacts for release as 3.11.2. > > sha1: 8a5e88f635fdb984505a99a553b5799cedccd06d > Git: > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a= > shortlog;h=refs/tags/3.11.2-tentative > Artifacts: > https://repository.apache.org/content/repositories/ > orgapachecassandra-1156/org/apache/cassandra/apache-cassandra/3.11.2/ > Staging repository: > https://repository.apache.org/content/repositories/ > orgapachecassandra-1156/ > > Debian and RPM packages are available here: > http://people.apache.org/~mshuler > > *** This release addresses an important fix for CASSANDRA-14092 *** > "Max ttl of 20 years will overflow localDeletionTime" > https://issues.apache.org/jira/browse/CASSANDRA-14092 > > The vote will be open for 72 hours (longer if needed). > > [1]: (CHANGES.txt) https://goo.gl/RLZLrR > [2]: (NEWS.txt) https://goo.gl/kpnVHp > >
Re: [VOTE] Release Apache Cassandra 2.2.12
+1 On Mon, Feb 12, 2018 at 1:02 PM, Brandon Williams wrote: > +1 > > On Mon, Feb 12, 2018 at 2:30 PM, Michael Shuler > wrote: > > > I propose the following artifacts for release as 2.2.12. > > > > sha1: 1602e606348959aead18531cb8027afb15f276e7 > > Git: > > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a= > > shortlog;h=refs/tags/2.2.12-tentative > > Artifacts: > > https://repository.apache.org/content/repositories/ > > orgapachecassandra-1153/org/apache/cassandra/apache-cassandra/2.2.12/ > > Staging repository: > > https://repository.apache.org/content/repositories/ > > orgapachecassandra-1153/ > > > > Debian and RPM packages are available here: > > http://people.apache.org/~mshuler > > > > *** This release addresses an important fix for CASSANDRA-14092 *** > > "Max ttl of 20 years will overflow localDeletionTime" > > https://issues.apache.org/jira/browse/CASSANDRA-14092 > > > > The vote will be open for 72 hours (longer if needed). > > > > [1]: (CHANGES.txt) https://goo.gl/QkJeXH > > [2]: (NEWS.txt) https://goo.gl/A4iKFb > > > > >
Re: [VOTE] Release Apache Cassandra 2.1.20
+1 On Mon, Feb 12, 2018 at 1:03 PM, Brandon Williams wrote: > +1 > > On Mon, Feb 12, 2018 at 2:30 PM, Michael Shuler > wrote: > > > I propose the following artifacts for release as 2.1.20. > > > > sha1: b2949439ec62077128103540e42570238520f4ee > > Git: > > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a= > > shortlog;h=refs/tags/2.1.20-tentative > > Artifacts: > > https://repository.apache.org/content/repositories/ > > orgapachecassandra-1152/org/apache/cassandra/apache-cassandra/2.1.20/ > > Staging repository: > > https://repository.apache.org/content/repositories/ > > orgapachecassandra-1152/ > > > > Debian and RPM packages are available here: > > http://people.apache.org/~mshuler > > > > *** This release addresses an important fix for CASSANDRA-14092 *** > > "Max ttl of 20 years will overflow localDeletionTime" > > https://issues.apache.org/jira/browse/CASSANDRA-14092 > > > > The vote will be open for 72 hours (longer if needed). > > > > [1]: (CHANGES.txt) https://goo.gl/5i2nw9 > > [2]: (NEWS.txt) https://goo.gl/i9Fg2u > > > > >
Re: Roadmap for 4.0
Advantages of cutting a release sooner than later: 1) The project needs to constantly progress forward. Releases are the most visible part of that. 2) Having a huge changelog in a release increases the likelihood of bugs that take time to find. Advantages of a slower release: 1) We don't do major versions often, and when we do breaking changes (protocol, file format, etc), we should squeeze in as many as possible to avoid having to roll new majors 2) There are probably few people actually running 3.11 at scale, so probably few people actually testing trunk. In terms of "big" changes I'd like to see land, the ones that come to mind are: https://issues.apache.org/jira/browse/CASSANDRA-9754 - "Birch" (changes file format) https://issues.apache.org/jira/browse/CASSANDRA-13442 - Transient Replicas (probably adds new replication strategy or similar) https://issues.apache.org/jira/browse/CASSANDRA-13628 - Rest of the internode netty stuff (no idea if this changes internode stuff, but I bet it's a lot easier if it lands on a major) https://issues.apache.org/jira/browse/CASSANDRA-7622 - Virtual Tables (selfish inclusion, probably doesn't need to be a major at all, and I wouldn't even lose sleep if it slips, but I'd like to see it land) Stuff I'm ok with slipping to 4.X or 5.0, but probably needs to land on a major because we'll change something big (like gossip, or the way schema is passed, etc): https://issues.apache.org/jira/browse/CASSANDRA-9667 - Strongly consistent membership https://issues.apache.org/jira/browse/CASSANDRA-10699 - Strongly consistent schema All that said, what I really care about is building confidence in the release, which means an extended testing cycle. If all of those patches landed tomorrow, I'd still expect us to be months away from a release, because we need to bake the next major - there's too many changes to throw out an alpha/beta/rc and hope someone actually runs it. I don't believe Q3/Q4 is realistic, but I may be biased (or jaded). It's possible Q3/Q4 alpha/beta is realistic, but definitely not a release. On Sun, Feb 11, 2018 at 8:29 PM, kurt greaves wrote: > Hi friends, > *TL;DR: Making a plan for 4.0, ideally everyone interested should provide > up to two lists, one for tickets they can contribute resources to getting > finished, and one for features they think would be desirable for 4.0, but > not necessarily have the resources to commit to helping with.* > > So we had that Roadmap for 4.0 discussion last year, but there was never a > conclusion or a plan that came from it. Times getting on and the changes > list for 4.0 is getting pretty big. I'm thinking it would probably make > sense to define some goals to getting 4.0 released/have an actual plan. 4.0 > is already going to be quite an unwieldy release with a lot of testing > required. > > Note: the following is open to discussion, if people don't like the plan > feel free to speak up. But in the end it's a pretty basic plan and I don't > think we should over-complicate it, I also don't want to end up in a > discussion where we "make a plan to make a plan". Regardless of whatever > plan we do end up following it would still be valuable to have a list of > tickets for 4.0 which is the overall goal of this email - so let's not get > too worked up on the details just yet (save that for after I > summarise/follow up). > > // TODO > I think the best way to go about this would be for us to come up with a > list of JIRA's that we want included in 4.0, tag these as 4.0, and all > other improvements as 4.x. We can then aim to release 4.0 once all the 4.0 > tagged tickets (+bug fixes/blockers) are complete. > > Now, the catch is that we obviously don't want to include too many tickets > in 4.0, but at the same time we want to make sure 4.0 has an appealing > feature set for both users/operators/developers. To minimise scope creep I > think the following strategy will help: > > We should maintain two lists: > >1. JIRA's that people want in 4.0 and can commit resources to getting >them implemented in 4.0. >2. JIRA's that people simply think would be desirable for 4.0, but >currently don't have anyone assigned to them or planned assignment. It >would probably make sense to label these with an additional tag in JIRA. > *(User's >please feel free to point out what you want here)* > > From list 1 will come our source of truth for when we release 4.0. (after > aggregating a list I will summarise and we can vote on it). > > List 2 would be the "hopeful" list, where stories can be picked up from if > resourcing allows, or where someone comes along and decides it's good > enough to work on. I guess we can also base this on a vote system if we > reach the point of including some of them. (but for the moment it's purely > to get an idea of what users actually want). > > Please don't refrain from listing something that's already been mentioned. > The purpose is to get an idea of everyone's priorities/interests
Re: [VOTE] (Take 2) Release Apache Cassandra 3.11.2
> I propose the following artifacts for release as 3.11.2. Thanks Michael for the recut, very much appreciated. +1 - To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org
Re: [VOTE] (Take 2) Release Apache Cassandra 3.11.2
+1 On Mon, Feb 12, 2018 at 9:51 PM mck wrote: > > > > I propose the following artifacts for release as 3.11.2. > > > Thanks Michael for the recut, very much appreciated. > > +1 > > > - > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org > For additional commands, e-mail: dev-h...@cassandra.apache.org > >
