Re: Failed Dtest will block cutting releases

2016-11-21 Thread Josh McKenzie
Caveat: I'm strongly in favor of us blocking a release on a non-green test board of either utest or dtest. > put something in prod which is known to be broken in obvious ways In my experience the majority of fixes are actually shoring up low-quality / flaky tests or fixing tests that have been

Re: Failed Dtest will block cutting releases

2016-11-21 Thread Jonathan Haddad
+1. Kind of silly to put advise people to put something in prod which is known to be broken in obvious ways On Mon, Nov 21, 2016 at 11:31 AM sankalp kohli wrote: > Hi, > We should not cut a releases if Dtest are not passing. I won't block > 3.10 on this since we are

Failed Dtest will block cutting releases

2016-11-21 Thread sankalp kohli
Hi, We should not cut a releases if Dtest are not passing. I won't block 3.10 on this since we are just discussing this. Please provide feedback on this. Thanks, Sankalp

Re: [VOTE] Release Apache Cassandra 3.10 (Take 3)

2016-11-21 Thread sankalp kohli
We voted in the dev list discussion[1] that we wont cut a release till all unit tests are passing. I can see that testall are failing for trunk and 3.X. Hence I need to do a -1 on this release. My -1 is not due to Dtest failing as we discussed about unit tests only in that thread. I will start

Re: Proposals for releases - 4.0 and beyond

2016-11-21 Thread Jonathan Haddad
+1 as well On Mon, Nov 21, 2016 at 10:59 AM kurt Greaves wrote: > yep +1 to this. The LTS release solves my previous concern >

Re: Proposals for releases - 4.0 and beyond

2016-11-21 Thread kurt Greaves
yep +1 to this. The LTS release solves my previous concern

Re: Status of dtest donation?

2016-11-21 Thread Jeff Jirsa
Incubator handles the ICLA / IP transfer for the subrepo. On 11/21/16, 10:11 AM, "Jonathan Ellis" wrote: >I thought we could just pull dtest into another repo managed by C* PMC. Do >we need to involve incubator? > >On Mon, Nov 21, 2016 at 11:50 AM, Nate McCall

Re: Cassandra Mutation object decoding

2016-11-21 Thread Sanal Vasudevan
Thank you Vladimir. Anyone else has any other ideas as to how this can be done? Many thanks, Sanal On Sun, Nov 20, 2016 at 4:46 AM, Vladimir Yudovin wrote: > Hi Sanal, > > > > do we have metadata inside Mutation object to decode whether the CQL > was an INSERT or UPDATE

Re: Status of dtest donation?

2016-11-21 Thread Jonathan Ellis
I thought we could just pull dtest into another repo managed by C* PMC. Do we need to involve incubator? On Mon, Nov 21, 2016 at 11:50 AM, Nate McCall wrote: > Not sure where we got with the ICLA (and I think filling out the > paperwork fell off my plate while we were

Re: Status of dtest donation?

2016-11-21 Thread Nate McCall
Not sure where we got with the ICLA (and I think filling out the paperwork fell off my plate while we were waiting to hear about that). I'll finish getting the forms together for the Incubator (again, incubation folks also handle review, we don't need to "incubate" dtest) since that was on me.

Re: [VOTE] Release Apache Cassandra 3.10 (Take 3)

2016-11-21 Thread Sankalp Kohli
We had decided in an email thread initiated by me that we won't cut releases till all tests are passing. Why not wait till these patches are merged? Is there any critical fix in it which need to be rushed out ? > On Nov 20, 2016, at 23:36, Oleksandr Petrov >

cassandra-3.11 and the new merge order

2016-11-21 Thread Benjamin Lerer
Hi, I created a new cassandra-3.11 branch. By consequence, the new merge order for bug fixe is: 2.2 -> 3.0.X -> 3.11 -> 3.X -> trunk and the new merge order for improvements is: 3.X -> trunk 3.X will then be released as 3.12 and trunk as 4.0. Benjamin

Re: Proposals for releases - 4.0 and beyond

2016-11-21 Thread Blake Eggleston
I really like Stefan's Ubuntu model (because of the LTS release), with Sylvain's suggestion a close second. Both because I think we should do a supported, non-dev release every 6 months, and release bug fixes for them for a at least a year. On November 19, 2016 at 10:30:02 AM, Stefan

Re: Status of dtest donation?

2016-11-21 Thread Jake Luciani
I think the main blocker is identifying and contacting the folks who have contributed code to dtest without an ICLA On Mon, Nov 21, 2016 at 4:40 AM, Dave Lester wrote: > I may have missed further email discussion or updates, but since the > October 3rd email accepting dtest

Status of dtest donation?

2016-11-21 Thread Dave Lester
I may have missed further email discussion or updates, but since the October 3rd email accepting dtest to the project has there been any movement? Nate, is this something you're driving? Best, Dave