Return-Path: Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: (qmail 36353 invoked from network); 18 Feb 2011 02:17:21 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 18 Feb 2011 02:17:21 -0000 Received: (qmail 14062 invoked by uid 500); 18 Feb 2011 02:17:19 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 13984 invoked by uid 500); 18 Feb 2011 02:17:18 -0000 Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@cassandra.apache.org Delivered-To: mailing list user@cassandra.apache.org Received: (qmail 13976 invoked by uid 99); 18 Feb 2011 02:17:18 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 18 Feb 2011 02:17:18 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_NONE X-Spam-Check-By: apache.org Received-SPF: unknown ipv4:173.13.187.41 (athena.apache.org: encountered unrecognized mechanism during SPF processing of domain of gregory.szorc@xobni.com) Received: from [168.144.250.246] (HELO xsmtp06.mail2web.com) (168.144.250.246) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 18 Feb 2011 02:17:12 +0000 Received: from [10.5.31.9] (helo=hub03.ad2.softcom.biz) by xsmtp06.mail2web.com with esmtps (TLS-1.0:RSA_ARCFOUR_MD5:16) (Exim 4.63) (envelope-from ) id 1PqFth-0004IW-CV for user@cassandra.apache.org; Thu, 17 Feb 2011 21:16:50 -0500 Received: from MBX71.ad2.softcom.biz ([10.5.13.39]) by hub03.ad2.softcom.biz ([10.5.31.9]) with mapi; Thu, 17 Feb 2011 21:16:37 -0500 From: Gregory Szorc To: "user@cassandra.apache.org" Date: Thu, 17 Feb 2011 21:16:37 -0500 Thread-Topic: Request For 0.6.12 Release Thread-Index: AcvPAdrBNids+svlTlmO0kf5cOb8XgADz/KQ Message-ID: <194F4910C0FBD242B62C3C2EE68BCA91370BF20F25@MBX71.ad2.softcom.biz> References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: multipart/alternative; boundary="_000_194F4910C0FBD242B62C3C2EE68BCA91370BF20F25MBX71ad2softc_" MIME-Version: 1.0 Subject: RE: Request For 0.6.12 Release --_000_194F4910C0FBD242B62C3C2EE68BCA91370BF20F25MBX71ad2softc_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Aaron, Thank you very much for initiating the voting process. I'm looking forward = to running this release. Was there any discussion around improving the communication of known issues= with releases? Gregory From: Aaron Morton [mailto:aaron@thelastpickle.com] Sent: Thursday, February 17, 2011 4:21 PM To: user@cassandra.apache.org Subject: Re: Request For 0.6.12 Release Gregory, There is a vote going on for 0.6.12 now http://www.mail-archive.com/dev@cassandra.apache.org/msg01808.html If you have time grab the bin and give it a test http://people.apache.org/~= eevans Aaron On 16 Feb, 2011,at 09:21 PM, Aaron Morton > wrote: Have checked it's all in the 0.6 branch and asked the devs for a 0.6.12 rel= ease. Will let you know how it goes. cheers Aaron On 16 Feb, 2011,at 08:38 AM, Aaron Morton > wrote: I worked on that ticket, will try to chase it up. Aaron On 15/02/2011, at 2:01 PM, Gregory Szorc > wrote: The latest official 0.6.x releases, 0.6.10 and 0.6.11, have a very serious = bug/regression when performing some quorum reads (CASSANDRA-2081), which is= fixed in the head of the 0.6 branch If there aren't any plans to cut 0.6.1= 2 any time soon, as an end user, I request that an official and "blessed" r= elease of 0.6.x be made ASAP. On a related note, I am frustrated that such a serious issue has lingered i= n the "latest oldstable release." I would have liked to see one or more of = the following: 1) The issue documented prominently on the apache.org web site and inside the download archive so end users would know they ar= e downloading and running known-broken software 2) The 0.6.10 and 0.6.11 builds pulled after identification of the iss= ue 3) A 0.6.12 release cut immediately (with reasonable time for testing,= of course) to address the issue I understand that releases may not always be as stable as we all desire. Bu= t, I hope that when future bugs affecting the bread and butter properties o= f a distributed storage engine surface (especially when they are regression= s) that the official project response (preferably via mailing list and the = web site) is swift and maximizes the potential for data integrity and avail= ability. If there is anything I can do to help the process, I'd gladly give some of = my time to help the overall community. Gregory Szorc gregory.szorc@gmail.com --_000_194F4910C0FBD242B62C3C2EE68BCA91370BF20F25MBX71ad2softc_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Aaron,

 

=

Thank you very much for initiating the voting p= rocess. I’m looking forward to running this release.

 

Was there any discussion around improving the communication o= f known issues with releases?

 

Gregory

 

=

From: Aaron Morton [mailto:aaron@thelastpickle.= com]
Sent: Thursday, February 17, 2011 4:21 PM
To: use= r@cassandra.apache.org
Subject: Re: Request For 0.6.12 Release

 

Gregory, 

There is a vote going on for 0.6.12 now 

 

If you have time grab the bin and give it a test http://people.apache.org/~eevans 

Aaron


On 16 Feb, 2011,at 09:2= 1 PM, Aaron Morton <aaron@the= lastpickle.com> wrote:

Have checked it's all in the 0.6 branch and asked= the devs for a 0.6.12 release. Will let you know how it goes.

cheers

Aaron


On 16 Feb, 2011,at 08:38 AM, Aaron Morton <aaron@thelastpickle.com> wrot= e:

I worked on that ticket, will tr= y to chase it up.

 =

 

<= p class=3DMsoNormal>Aaron



On 15/02/2011, at 2:01 PM, Gregory Szor= c <gregory.szorc@gmail.com> wrote:

=

The latest official 0.6.x releases, 0.6.10 and 0.6.11, have a v= ery serious bug/regression when performing some quorum reads (CASSANDRA-208= 1), which is fixed in the head of the 0.6 branch If there aren’t any = plans to cut 0.6.12 any time soon, as an end user, I request that an offici= al and “blessed” release of 0.6.x be made ASAP.

<= p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:= auto'> 

On a related note, I am frustrated that s= uch a serious issue has lingered in the “latest oldstable release.= 221; I would have liked to see one or more of the following:

=

 

1)      = The issue documented prominently on the apache.org web site and inside the download archive so end users woul= d know they are downloading and running known-broken software

2)      The 0.6.10 and 0.6.1= 1 builds pulled after identification of the issue

3)      A 0.6.12 release cut immediately= (with reasonable time for testing, of course) to address the issue

 

I understand that releases may no= t always be as stable as we all desire. But, I hope that when future bugs a= ffecting the bread and butter properties of a distributed storage engine su= rface (especially when they are regressions) that the official project resp= onse (preferably via mailing list and the web site) is swift and maximizes = the potential for data integrity and availability.

&= nbsp;

If there is anything I can do to help the proces= s, I’d gladly give some of my time to help the overall community.

 

Gregory Szorc

<= p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:= auto'>gregory.szorc@gmail.com

 

=
= --_000_194F4910C0FBD242B62C3C2EE68BCA91370BF20F25MBX71ad2softc_--