Re: [VOTE] Release Apache Cassandra 3.8

2016-09-27 Thread Tyler Hobbs
+1 On Mon, Sep 26, 2016 at 9:52 AM, Michael Shuler wrote: > I propose the following artifacts for release as 3.8. > > sha1: ce609d19fd130e16184d9e6d37ffee4a1ebad607 > Git: > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a= > shortlog;h=refs/tags/3.8-tentative >

Re: [VOTE] Release Apache Cassandra 3.8

2016-09-27 Thread Gary Dusbabek
+1 On Mon, Sep 26, 2016 at 9:52 AM, Michael Shuler wrote: > I propose the following artifacts for release as 3.8. > > sha1: ce609d19fd130e16184d9e6d37ffee4a1ebad607 > Git: > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a= > shortlog;h=refs/tags/3.8-tentative >

Re: [VOTE] Release Apache Cassandra 3.8

2016-09-27 Thread Aleksey Yeschenko
+1 --  AY On 26 September 2016 at 15:52:26, Michael Shuler (mich...@pbandjelly.org) wrote: I propose the following artifacts for release as 3.8. sha1: ce609d19fd130e16184d9e6d37ffee4a1ebad607 Git: http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.8-tentative

Re: [VOTE] Release Apache Cassandra 3.8

2016-09-27 Thread Sam Tunnicliffe
+1 On Mon, Sep 26, 2016 at 3:52 PM, Michael Shuler wrote: > I propose the following artifacts for release as 3.8. > > sha1: ce609d19fd130e16184d9e6d37ffee4a1ebad607 > Git: > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a= > shortlog;h=refs/tags/3.8-tentative >

Re: [VOTE] Release Apache Cassandra 3.8

2016-09-27 Thread Sylvain Lebresne
+1 On Tue, Sep 27, 2016 at 3:03 AM, Jeff Jirsa wrote: > > +1 > > On 2016-09-26 07:52 (-0700), Michael Shuler > wrote: > > I propose the following artifacts for release as 3.8. > > > > sha1: ce609d19fd130e16184d9e6d37ffee4a1ebad607 > > Git: > >

Re: [VOTE] Release Apache Cassandra 3.8

2016-09-26 Thread Jeff Jirsa
+1 On 2016-09-26 07:52 (-0700), Michael Shuler wrote: > I propose the following artifacts for release as 3.8. > > sha1: ce609d19fd130e16184d9e6d37ffee4a1ebad607 > Git: > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.8-tentative >

Re: [VOTE] Release Apache Cassandra 3.8

2016-09-26 Thread Nate McCall
+1 On Tue, Sep 27, 2016 at 3:52 AM, Michael Shuler wrote: > I propose the following artifacts for release as 3.8. > > sha1: ce609d19fd130e16184d9e6d37ffee4a1ebad607 > Git: > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.8-tentative >

Re: [VOTE] Release Apache Cassandra 3.8

2016-07-28 Thread Tyler Hobbs
Agreed, option #2 is my preference as well. On Thu, Jul 28, 2016 at 2:04 PM, Dave Brosius wrote: > Option Two seems reasonable to me > > > --- > > > > On 2016-07-28 14:47, Aleksey Yeschenko wrote: > >> Jake was just swapping his vote +1 to -1. >> >> Swapping mine to

Re: [VOTE] Release Apache Cassandra 3.8

2016-07-28 Thread Dave Brosius
Option Two seems reasonable to me --- On 2016-07-28 14:47, Aleksey Yeschenko wrote: Jake was just swapping his vote +1 to -1. Swapping mine to -1 too, so that we have a binding -1 majority now. Let’s get #12236 in and then decide what to do. --  AY On 28 July 2016 at 19:46:56, Benedict

Re: [VOTE] Release Apache Cassandra 3.8

2016-07-28 Thread Aleksey Yeschenko
Jake was just swapping his vote +1 to -1. Swapping mine to -1 too, so that we have a binding -1 majority now. Let’s get #12236 in and then decide what to do. --  AY On 28 July 2016 at 19:46:56, Benedict Elliott Smith (bened...@apache.org) wrote: I think -1 lacks a little clarity when

Re: [VOTE] Release Apache Cassandra 3.8

2016-07-21 Thread Brian Hess
I have no vote here, but I think that #2 is not a good idea here. We would be implicitly releasing an "odd" release with new features, which is more than a little confusing. I do think that CDC is important, so I don't like #4 (but for less important reasons than #2). So, I'm good with options

Re: [VOTE] Release Apache Cassandra 3.8

2016-07-21 Thread Aleksey Yeschenko
What we’d usually do is revert the offending ticket and push it to the next release, if this indeed were significant enough. So option 4 would be to revert CDC fast (painful) and ship. Option 5 would be to quickly fix the issue, retag, and revote, with 3.9 still following up on schedule. Option

Re: [VOTE] Release Apache Cassandra 3.8

2016-07-21 Thread Sylvain Lebresne
On Thu, Jul 21, 2016 at 3:21 PM, Jonathan Ellis wrote: > I see the alternatives as: > > 1. Release this as 3.8 > 2. Skip 3.8 and release 3.9 next month on schedule > 3. Skip this month and release 3.8 next month instead > I've hopefully made it clear I don't really like 1.

Re: [VOTE] Release Apache Cassandra 3.8

2016-07-21 Thread Jonathan Ellis
I see the alternatives as: 1. Release this as 3.8 2. Skip 3.8 and release 3.9 next month on schedule 3. Skip this month and release 3.8 next month instead On Thu, Jul 21, 2016 at 8:19 AM, Aleksey Yeschenko wrote: > I still think the issue is minor enough, and with 3.8

Re: [VOTE] Release Apache Cassandra 3.8

2016-07-21 Thread Aleksey Yeschenko
I still think the issue is minor enough, and with 3.8 being extremely delayed, and being a non-odd release, at that, we’d be better off just pushing it. Also, I know we’ve been easy on -1s when voting on releases, but I want to remind people in general that release votes can not be vetoed and

Re: [VOTE] Release Apache Cassandra 3.8

2016-07-21 Thread Sylvain Lebresne
Sorry but I'm (binding) -1 on this because of https://issues.apache.org/jira/browse/CASSANDRA-12236. I disagree that knowingly releasing a version that will temporarily break in-flight queries during upgrade, even if it's for a very short time-frame until re-connection, is ok. I'll note in

Re: [VOTE] Release Apache Cassandra 3.8

2016-07-20 Thread Dave Brosius
+1 On 07/20/2016 05:48 PM, Michael Shuler wrote: I propose the following artifacts for release as 3.8. sha1: c3ded0551f538f7845602b27d53240cd8129265c Git: http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.8-tentative Artifacts:

Re: [VOTE] Release Apache Cassandra 3.8

2016-07-20 Thread Robert Stupp
+1 — Robert Stupp @snazy > On 21 Jul 2016, at 07:48, Michael Shuler wrote: > > I propose the following artifacts for release as 3.8. > > sha1: c3ded0551f538f7845602b27d53240cd8129265c > Git: >

Re: [VOTE] Release Apache Cassandra 3.8

2016-07-20 Thread Josh McKenzie
+1 On Wed, Jul 20, 2016 at 5:48 PM, Michael Shuler wrote: > I propose the following artifacts for release as 3.8. > > sha1: c3ded0551f538f7845602b27d53240cd8129265c > Git: > > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.8-tentative >

Re: [VOTE] Release Apache Cassandra 3.8

2016-07-20 Thread Pavel Yaskevich
+1 On Wed, Jul 20, 2016 at 5:09 PM, Aleksey Yeschenko wrote: > +1 > > -- > AY > > On 20 July 2016 at 22:48:09, Michael Shuler (mshu...@apache.org) wrote: > > I propose the following artifacts for release as 3.8. > > sha1: c3ded0551f538f7845602b27d53240cd8129265c > Git: > >

Re: [VOTE] Release Apache Cassandra 3.8

2016-07-20 Thread Aleksey Yeschenko
+1 --  AY On 20 July 2016 at 22:48:09, Michael Shuler (mshu...@apache.org) wrote: I propose the following artifacts for release as 3.8. sha1: c3ded0551f538f7845602b27d53240cd8129265c Git: http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.8-tentative

Re: [VOTE] Release Apache Cassandra 3.8

2016-07-20 Thread Jake Luciani
+1 On Wed, Jul 20, 2016 at 6:04 PM, Brandon Williams wrote: > +1 > > On Wed, Jul 20, 2016 at 4:48 PM, Michael Shuler > wrote: > > > I propose the following artifacts for release as 3.8. > > > > sha1: c3ded0551f538f7845602b27d53240cd8129265c > > Git: > > >

Re: [VOTE] Release Apache Cassandra 3.8

2016-07-20 Thread Brandon Williams
+1 On Wed, Jul 20, 2016 at 4:48 PM, Michael Shuler wrote: > I propose the following artifacts for release as 3.8. > > sha1: c3ded0551f538f7845602b27d53240cd8129265c > Git: > > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.8-tentative >