Re: [VOTE] Release Apache Cassandra 3.0.10 (Take 2)
+1 On Tue, Nov 8, 2016 at 8:08 PM, Michael Shuler wrote: > I propose the following artifacts for release as 3.0.10. > > sha1: 4e0bced5e6a82ebd22b074b8ef96d930c5f3159d > Git: > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a= > shortlog;h=refs/tags/3.0.10-tentative > Artifacts: > https://repository.apache.org/content/repositories/ > orgapachecassandra-1132/org/apache/cassandra/apache-cassandra/3.0.10/ > Staging repository: > https://repository.apache.org/content/repositories/ > orgapachecassandra-1132/ > > The Debian packages are available here: http://people.apache.org/~mshuler > > The vote will be open for 72 hours (longer if needed). > > [1]: (CHANGES.txt) https://goo.gl/mnmZgI > [2]: (NEWS.txt) https://goo.gl/F1kAmR >
Re: [VOTE] Release Apache Cassandra 3.10 (Take 2)
+1 On Tue, Nov 8, 2016 at 8:09 PM, Michael Shuler wrote: > I propose the following artifacts for release as 3.10. > > sha1: 072b5271a88328b909b230d0e30df1c7476fdb3f > Git: > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a= > shortlog;h=refs/tags/3.10-tentative > Artifacts: > https://repository.apache.org/content/repositories/ > orgapachecassandra-1133/org/apache/cassandra/apache-cassandra/3.10/ > Staging repository: > https://repository.apache.org/content/repositories/ > orgapachecassandra-1133/ > > > > The Debian packages are available here: > http://people.apache.org/~mshuler > > > > The vote will be open for 72 hours (longer if needed). > > > > [1]: (CHANGES.txt) https://goo.gl/TZa9a7 > > [2]: (NEWS.txt) https://goo.gl/FSI1a4 >
Re: Moderation
On Mon, Nov 07, 2016 at 09:01:39AM +, Ross Gardler wrote: > Because of the way we are structured from an operations point of view or is > necessary to have s commit bit to be a PMC member. However, that doesn't mean > one needs to commit code. > > A good PMC member looks after the health of the community. They do not > necessarily write code. We have foundation members who have never committed a > line of code. See also a recent discussion on this topic here: https://lists.apache.org/thread.html/7b5f8b3475838c2312fcdac8cb8b88e5c2ac1a05e958d106c90a1fc8@%3Cdev.community.apache.org%3E https://www.apache.org/foundation/getinvolved.html#become-a-committer Cheers, Isabel
Re: [VOTE] Release Apache Cassandra 3.10 (Take 2)
-1 Sorry but I have to -1 that one, with the following explanation One of the features in 3.10 breaks SASI in quite a significant way. The issue was introduced in #11990 [1] and described in #12877 [2]. If there are more than 8 items in partition that have same index value, index file will get corrupted and returned results will be incorrect. I think we should rather revert the patch and go ahead with a release without it and change the patch to work correctly, possibly making it's scope slightly bigger. I am working on a design document for the change. [1] https://issues.apache.org/jira/browse/CASSANDRA-11990 [2] https://issues.apache.org/jira/browse/CASSANDRA-12877 On Wed, Nov 9, 2016 at 11:19 AM Gary Dusbabek wrote: > +1 > > On Tue, Nov 8, 2016 at 8:09 PM, Michael Shuler > wrote: > > > I propose the following artifacts for release as 3.10. > > > > sha1: 072b5271a88328b909b230d0e30df1c7476fdb3f > > Git: > > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a= > > shortlog;h=refs/tags/3.10-tentative > > Artifacts: > > https://repository.apache.org/content/repositories/ > > orgapachecassandra-1133/org/apache/cassandra/apache-cassandra/3.10/ > > Staging repository: > > https://repository.apache.org/content/repositories/ > > orgapachecassandra-1133/ > > > > > > > > The Debian packages are available here: > > http://people.apache.org/~mshuler > > > > > > > > The vote will be open for 72 hours (longer if needed). > > > > > > > > [1]: (CHANGES.txt) https://goo.gl/TZa9a7 > > > > [2]: (NEWS.txt) https://goo.gl/FSI1a4 > > > -- Alex Petrov
Re: [VOTE] Release Apache Cassandra 3.10 (Take 2)
-1 from me too due to #12877. I also agree with Alex's suggestion of reverting #11990 and re-rolling. On Wed, Nov 9, 2016 at 1:20 PM, Oleksandr Petrov wrote: > -1 > > Sorry but I have to -1 that one, with the following explanation > > One of the features in 3.10 breaks SASI in quite a significant way. The > issue was introduced in #11990 [1] and described in #12877 [2]. If there > are more than 8 items in partition that have same index value, index file > will get corrupted and returned results will be incorrect. > > I think we should rather revert the patch and go ahead with a release > without it and change the patch to work correctly, possibly making it's > scope slightly bigger. I am working on a design document for the change. > > [1] https://issues.apache.org/jira/browse/CASSANDRA-11990 > [2] https://issues.apache.org/jira/browse/CASSANDRA-12877 > > On Wed, Nov 9, 2016 at 11:19 AM Gary Dusbabek wrote: > > > +1 > > > > On Tue, Nov 8, 2016 at 8:09 PM, Michael Shuler > > wrote: > > > > > I propose the following artifacts for release as 3.10. > > > > > > sha1: 072b5271a88328b909b230d0e30df1c7476fdb3f > > > Git: > > > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a= > > > shortlog;h=refs/tags/3.10-tentative > > > Artifacts: > > > https://repository.apache.org/content/repositories/ > > > orgapachecassandra-1133/org/apache/cassandra/apache-cassandra/3.10/ > > > Staging repository: > > > https://repository.apache.org/content/repositories/ > > > orgapachecassandra-1133/ > > > > > > > > > > > > The Debian packages are available here: > > > http://people.apache.org/~mshuler > > > > > > > > > > > > The vote will be open for 72 hours (longer if needed). > > > > > > > > > > > > [1]: (CHANGES.txt) https://goo.gl/TZa9a7 > > > > > > [2]: (NEWS.txt) https://goo.gl/FSI1a4 > > > > > > -- > Alex Petrov >
Re: [VOTE] Release Apache Cassandra 3.0.10 (Take 2)
+1 On Tue, Nov 8, 2016 at 2:08 PM, Michael Shuler wrote: > I propose the following artifacts for release as 3.0.10. > > sha1: 4e0bced5e6a82ebd22b074b8ef96d930c5f3159d > Git: > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a= > shortlog;h=refs/tags/3.0.10-tentative > Artifacts: > https://repository.apache.org/content/repositories/ > orgapachecassandra-1132/org/apache/cassandra/apache-cassandra/3.0.10/ > Staging repository: > https://repository.apache.org/content/repositories/ > orgapachecassandra-1132/ > > The Debian packages are available here: http://people.apache.org/~mshuler > > The vote will be open for 72 hours (longer if needed). > > [1]: (CHANGES.txt) https://goo.gl/mnmZgI > [2]: (NEWS.txt) https://goo.gl/F1kAmR >
Re: [VOTE] Release Apache Cassandra 3.10 (Take 2)
Good catch. Thanks everyone for speaking up about these. Changing mine to -1 On Nov 10, 2016 2:44 AM, "Sam Tunnicliffe" wrote: > > -1 from me too due to #12877. I also agree with Alex's suggestion of > reverting #11990 and re-rolling. > > On Wed, Nov 9, 2016 at 1:20 PM, Oleksandr Petrov < oleksandr.pet...@gmail.com > > wrote: > > > -1 > > > > Sorry but I have to -1 that one, with the following explanation > > > > One of the features in 3.10 breaks SASI in quite a significant way. The > > issue was introduced in #11990 [1] and described in #12877 [2]. If there > > are more than 8 items in partition that have same index value, index file > > will get corrupted and returned results will be incorrect. > > > > I think we should rather revert the patch and go ahead with a release > > without it and change the patch to work correctly, possibly making it's > > scope slightly bigger. I am working on a design document for the change. > > > > [1] https://issues.apache.org/jira/browse/CASSANDRA-11990 > > [2] https://issues.apache.org/jira/browse/CASSANDRA-12877 > > > > On Wed, Nov 9, 2016 at 11:19 AM Gary Dusbabek wrote: > > > > > +1 > > > > > > On Tue, Nov 8, 2016 at 8:09 PM, Michael Shuler > > > wrote: > > > > > > > I propose the following artifacts for release as 3.10. > > > > > > > > sha1: 072b5271a88328b909b230d0e30df1c7476fdb3f > > > > Git: > > > > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a= > > > > shortlog;h=refs/tags/3.10-tentative > > > > Artifacts: > > > > https://repository.apache.org/content/repositories/ > > > > orgapachecassandra-1133/org/apache/cassandra/apache-cassandra/3.10/ > > > > Staging repository: > > > > https://repository.apache.org/content/repositories/ > > > > orgapachecassandra-1133/ > > > > > > > > > > > > > > > > The Debian packages are available here: > > > > http://people.apache.org/~mshuler > > > > > > > > > > > > > > > > The vote will be open for 72 hours (longer if needed). > > > > > > > > > > > > > > > > [1]: (CHANGES.txt) https://goo.gl/TZa9a7 > > > > > > > > [2]: (NEWS.txt) https://goo.gl/FSI1a4 > > > > > > > > > -- > > Alex Petrov > >
Re: [VOTE] Release Apache Cassandra 3.10 (Take 2)
-1 as well, #12877 On 11/9/16, 5:20 AM, "Oleksandr Petrov" wrote: >-1 > >Sorry but I have to -1 that one, with the following explanation > >One of the features in 3.10 breaks SASI in quite a significant way. The >issue was introduced in #11990 [1] and described in #12877 [2]. If there >are more than 8 items in partition that have same index value, index file >will get corrupted and returned results will be incorrect. > >I think we should rather revert the patch and go ahead with a release >without it and change the patch to work correctly, possibly making it's >scope slightly bigger. I am working on a design document for the change. > >[1] >https://urldefense.proofpoint.com/v2/url?u=https-3A__issues.apache.org_jira_browse_CASSANDRA-2D11990&d=DgIBaQ&c=08AGY6txKsvMOP6lYkHQpPMRA1U6kqhAwGa8-0QCg3M&r=yfYEBHVkX6l0zImlOIBID0gmhluYPD5Jje-3CtaT3ow&m=ibGDVaeFlUoJ_RF8g3otJoEFCZNVwQ38FDLHoRH2WpE&s=1LFYHLGHFPYzM7jDJ56_7SKYBJIqpCHsxr0taxZ3nS4&e= > >[2] >https://urldefense.proofpoint.com/v2/url?u=https-3A__issues.apache.org_jira_browse_CASSANDRA-2D12877&d=DgIBaQ&c=08AGY6txKsvMOP6lYkHQpPMRA1U6kqhAwGa8-0QCg3M&r=yfYEBHVkX6l0zImlOIBID0gmhluYPD5Jje-3CtaT3ow&m=ibGDVaeFlUoJ_RF8g3otJoEFCZNVwQ38FDLHoRH2WpE&s=1YjohT2-dB9Ye9MXGCUpVsGY6Ot1CH9v_PSHPS2eUkE&e= > > >On Wed, Nov 9, 2016 at 11:19 AM Gary Dusbabek wrote: > >> +1 >> >> On Tue, Nov 8, 2016 at 8:09 PM, Michael Shuler >> wrote: >> >> > I propose the following artifacts for release as 3.10. >> > >> > sha1: 072b5271a88328b909b230d0e30df1c7476fdb3f >> > Git: >> > https://urldefense.proofpoint.com/v2/url?u=http-3A__git-2Dwip-2Dus.apache.org_repos_asf-3Fp-3Dcassandra.git-3Ba-3D&d=DgIBaQ&c=08AGY6txKsvMOP6lYkHQpPMRA1U6kqhAwGa8-0QCg3M&r=yfYEBHVkX6l0zImlOIBID0gmhluYPD5Jje-3CtaT3ow&m=ibGDVaeFlUoJ_RF8g3otJoEFCZNVwQ38FDLHoRH2WpE&s=Yf3E6uBirmkRTS3IE9xB7oPxz0EpbOc1rdiF9-qei-8&e= >> > >> > shortlog;h=refs/tags/3.10-tentative >> > Artifacts: >> > https://urldefense.proofpoint.com/v2/url?u=https-3A__repository.apache.org_content_repositories_&d=DgIBaQ&c=08AGY6txKsvMOP6lYkHQpPMRA1U6kqhAwGa8-0QCg3M&r=yfYEBHVkX6l0zImlOIBID0gmhluYPD5Jje-3CtaT3ow&m=ibGDVaeFlUoJ_RF8g3otJoEFCZNVwQ38FDLHoRH2WpE&s=V5SCV7GU7VFuWN4xr05zJpEUaz2FoPWBjlZQRZtLXDE&e= >> > >> > orgapachecassandra-1133/org/apache/cassandra/apache-cassandra/3.10/ >> > Staging repository: >> > https://urldefense.proofpoint.com/v2/url?u=https-3A__repository.apache.org_content_repositories_&d=DgIBaQ&c=08AGY6txKsvMOP6lYkHQpPMRA1U6kqhAwGa8-0QCg3M&r=yfYEBHVkX6l0zImlOIBID0gmhluYPD5Jje-3CtaT3ow&m=ibGDVaeFlUoJ_RF8g3otJoEFCZNVwQ38FDLHoRH2WpE&s=V5SCV7GU7VFuWN4xr05zJpEUaz2FoPWBjlZQRZtLXDE&e= >> > >> > orgapachecassandra-1133/ >> > >> > >> > >> > The Debian packages are available here: >> > https://urldefense.proofpoint.com/v2/url?u=http-3A__people.apache.org_-7Emshuler&d=DgIBaQ&c=08AGY6txKsvMOP6lYkHQpPMRA1U6kqhAwGa8-0QCg3M&r=yfYEBHVkX6l0zImlOIBID0gmhluYPD5Jje-3CtaT3ow&m=ibGDVaeFlUoJ_RF8g3otJoEFCZNVwQ38FDLHoRH2WpE&s=tcexRsY-LYWRWDsXlNurHM0-GsKvwf4CQsz52uGNCcI&e= >> > >> > >> > >> > >> > The vote will be open for 72 hours (longer if needed). >> > >> > >> > >> > [1]: (CHANGES.txt) >> > https://urldefense.proofpoint.com/v2/url?u=https-3A__goo.gl_TZa9a7&d=DgIBaQ&c=08AGY6txKsvMOP6lYkHQpPMRA1U6kqhAwGa8-0QCg3M&r=yfYEBHVkX6l0zImlOIBID0gmhluYPD5Jje-3CtaT3ow&m=ibGDVaeFlUoJ_RF8g3otJoEFCZNVwQ38FDLHoRH2WpE&s=EJsg6DC55Ir-63UXhcs2eTtjm8UwxU13WmDWyoqD62Q&e= >> > >> > >> > [2]: (NEWS.txt) >> > https://urldefense.proofpoint.com/v2/url?u=https-3A__goo.gl_FSI1a4&d=DgIBaQ&c=08AGY6txKsvMOP6lYkHQpPMRA1U6kqhAwGa8-0QCg3M&r=yfYEBHVkX6l0zImlOIBID0gmhluYPD5Jje-3CtaT3ow&m=ibGDVaeFlUoJ_RF8g3otJoEFCZNVwQ38FDLHoRH2WpE&s=FXC91mnGnVTHsJd3v6wJ2isKVd2PEBH78JUyQtYDVyo&e= >> > >> > >> >-- >Alex Petrov smime.p7s Description: S/MIME cryptographic signature
Re: Broader community involvement in 4.0 (WAS Re: Rough roadmap for 4.0)
I like the idea of a goal-based approach. I think that would make coming to a consensus a bit easier particularly if a larger number of people are involved. On Tue, Nov 8, 2016 at 8:04 PM, Dikang Gu wrote: > My 2 cents. I'm wondering is it a good idea to have some high level goals > for the major release? For example, the goals could be something like: > 1. Improve the scalability/reliability/performance by X%. > 2. Add Y new features (feature A, B, C, D...). > 3. Fix Z known issues (issue A, B, C, D...). > > I feel If we can have the high level goals, it would be easy to pick the > jiras to be included in the release. > > Does it make sense? > > Thanks > Dikang. > > On Mon, Nov 7, 2016 at 11:22 AM, Oleksandr Petrov < > oleksandr.pet...@gmail.com> wrote: > >> Recently there was another discussion on documentation and comments [1] >> >> On one hand, documentation and comments will help newcomers to familiarise >> themselves with the codebase. On the other - one may get up to speed by >> reading the code and adding some docs. Such things may require less >> oversight and can play some role in improving diversity / increasing an >> amount of involved people. >> >> Same thing with tests. There are some areas where tests need some >> refactoring / improvements, or even just splitting them from one file to >> multiple. It's a good way to experience the process and get involved into >> discussion. >> >> For that, we could add some issues with subtasks (just a few for starters) >> or even just a wiki page with a doc/test wishlist where everyone could add >> a couple of points. >> >> Docs and tests could be used in addition to lhf issues, helping people, >> having comprehensive and quick process and everything else that was >> mentioned in this thread. >> >> Thank you. >> >> [1] >> http://mail-archives.apache.org/mod_mbox/cassandra-dev/201605.mbox/% >> 3ccakkz8q088ojbvhycyz2_2eotqk4y-svwiwksinpt6rr9pop...@mail.gmail.com%3E >> >> On Mon, Nov 7, 2016 at 5:38 PM Aleksey Yeschenko >> wrote: >> >> > Agreed. >> > >> > -- >> > AY >> > >> > On 7 November 2016 at 16:38:07, Jeff Jirsa (jeff.ji...@crowdstrike.com) >> > wrote: >> > >> > ‘Accepted’ JIRA status seems useful, but would encourage something more >> > explicit like ‘Concept Accepted’ or similar to denote that the concept is >> > agreed upon, but the actual patch itself may not be accepted yet. >> > >> > /bikeshed. >> > >> > On 11/7/16, 2:56 AM, "Ben Slater" wrote: >> > >> > >Thanks Dave. The shepherd concept sounds a lot like I had in mind (and a >> > >better name). >> > > >> > >One other thing I noted from the Mesos process - they have an “Accepted” >> > >jira status that comes after open and means “at least one Mesos >> developer >> > >thought that the ideas proposed in the issue are worth pursuing >> further”. >> > >Might also be something to consider as part of a process like this? >> > > >> > >Cheers >> > >Ben >> > > >> > >On Mon, 7 Nov 2016 at 09:37 Dave Lester wrote: >> > > >> > >> Hi Ben, >> > >> >> > >> A few ideas to add to your suggestions [inline]: >> > >> >> > >> On 2016-11-06 13:51 (-0800), Ben Slater < >> > https://urldefense.proofpoint.com/v2/url?u=http-3A__ben. >> slater-40instaclustr.com&d=DgIFaQ&c=08AGY6txKsvMOP6lYkHQpPMRA1U6kq >> hAwGa8-0QCg3M&r=yfYEBHVkX6l0zImlOIBID0gmhluYPD5Jje-3CtaT3ow&m= >> 0Ynrto5MaNdgc2fOUtxv50ouikBU_P7VEv6KNub9Bhk&s= >> MAZTdq4wfrTiqh7nImEMcFWtTrsixRFOX7Pi0SKqQv0&e= >> > > >> > >> wrote: >> > >> > Hi All, >> > >> > >> > >> > I thought I would add a couple of observations and suggestions as >> > someone >> > >> > who has both personally made my first contributions to the project >> in >> > the >> > >> > last few months and someone in a leadership role in an organisation >> > >> > (Instaclustr) that is feeling it’s way through increasing our >> > >> contributions >> > >> > as an organisation. >> > >> > >> > >> > Firstly - an observation on contribution experience and what I think >> > is >> > >> > likely to make people want to contribute again: >> > >> > 1) The worst thing that can happen is for your contribution to be >> > >> > completely ignored. >> > >> > 2) The second worst thing is for it to be rejected without a good >> > >> > explanation (that you can learn from) or with hostility. >> > >> > 3) Having it rejected with a good reason is not a bad thing (you >> > learn) >> > >> > 4) Having it accepted is, of course, the best! >> > >> > >> > >> > With this as a background I would suggest a couple of thing that >> help >> > >> make >> > >> > sure (3) and (4) are always more common that (1) and (2) (good >> > outcomes >> > >> are >> > >> > probably more common than bad at the moment but we’ve experienced >> all >> > >> four >> > >> > scenarios in the last few months): >> > >> > 1) I think some process of assigning a committer of a “sponsor” of a >> > >> change >> > >> > (which would probably mean committers volunteering) before it >> > commences >> > >> > would be useful. You can kind of do this at the moment by creat
[RESULT] [VOTE] Close client-...@cassandra.apache.org mailing list
With 8 binding +1s (including myself), 3 non-binding +1, and no -1, the vote passes, and we'll work to close out this list. - Jeff On 2016-11-06 21:11 (-0800), "Jeff Jirsa" wrote: > There exists a nearly unused mailing list, client-...@cassandra.apache.org > [0]. > > This is a summary of the email threads over the past 12 months on that list: > > 1) ApacheCon Seville CFP Close notice > 2) Datastax .NET driver question > 3) Datastax Java driver question > 4) FOSDEM announce > 5) ApacheCon NA CFP Open noticed > > In order to avoid confusion, and given the lack of relevant and appropriate > traffic, I propose we close the client-dev@ list entirely. Any traffic > appropriate for the client-dev@ list would likely be better served if it were > directed at dev@, which is more active. > > This vote will remain open for 72 hours. > > 0: https://lists.apache.org/list.html?client-...@cassandra.apache.org > > >
