Return-Path: X-Original-To: apmail-cloudstack-dev-archive@www.apache.org Delivered-To: apmail-cloudstack-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 42582CDCE for ; Mon, 3 Jun 2013 18:10:46 +0000 (UTC) Received: (qmail 29618 invoked by uid 500); 3 Jun 2013 18:10:45 -0000 Delivered-To: apmail-cloudstack-dev-archive@cloudstack.apache.org Received: (qmail 29579 invoked by uid 500); 3 Jun 2013 18:10:45 -0000 Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cloudstack.apache.org Delivered-To: mailing list dev@cloudstack.apache.org Received: (qmail 29571 invoked by uid 99); 3 Jun 2013 18:10:45 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 Jun 2013 18:10:45 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of animesh.chaturvedi@citrix.com designates 66.165.176.63 as permitted sender) Received: from [66.165.176.63] (HELO SMTP02.CITRIX.COM) (66.165.176.63) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 Jun 2013 18:10:40 +0000 X-IronPort-AV: E=Sophos;i="4.87,794,1363132800"; d="scan'208";a="27568989" Received: from sjcpex01cl01.citrite.net ([10.216.14.143]) by FTLPIPO02.CITRIX.COM with ESMTP/TLS/AES128-SHA; 03 Jun 2013 18:09:52 +0000 Received: from SJCPEX01CL02.citrite.net ([169.254.2.64]) by SJCPEX01CL01.citrite.net ([169.254.1.43]) with mapi id 14.02.0342.003; Mon, 3 Jun 2013 11:09:51 -0700 From: Animesh Chaturvedi To: "dev@cloudstack.apache.org" Subject: RE: [VOTE] Pushback 4.2.0 Feature Freeze Thread-Topic: [VOTE] Pushback 4.2.0 Feature Freeze Thread-Index: AQHOXg+8drVsa4/qxkS4H1m6/8fmIJkkOR1wgAAVreA= Date: Mon, 3 Jun 2013 18:09:51 +0000 Message-ID: References: <20130531150021.GK25016@USLT-205755.sungardas.corp> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.216.48.12] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org +1 [binding] > -----Original Message----- > From: Animesh Chaturvedi [mailto:animesh.chaturvedi@citrix.com] > Sent: Monday, June 03, 2013 10:32 AM > To: dev@cloudstack.apache.org > Subject: RE: [VOTE] Pushback 4.2.0 Feature Freeze >=20 >=20 > +1 to move feature freeze date to 6/28 to get in the features proposed > earlier for 4.2 and have a longer bug fix cycle. >=20 > After moving 103 open 4.1 targeted defects to 4.2 we will have total of > 367 open defects for 4.2. I hope with this change we are able to resolve > lot more defects before RC and we can get 4.2 out the door with fewer RC > re-spin. >=20 > Since all the other dates move out by 4 weeks means the feature proposal > freeze date which was originally at 5/04 would have been 6/1 which means > we are already past that, so no new feature proposals for 4.2. Any new > feature proposal will have to be targeted for 4.3 or beyond. >=20 >=20 > Thanks >=20 > Animesh >=20 >=20 >=20 >=20 >=20 > > -----Original Message----- > > From: Chip Childers [mailto:chip.childers@sungard.com] > > Sent: Friday, May 31, 2013 8:00 AM > > To: dev@cloudstack.apache.org > > Subject: [VOTE] Pushback 4.2.0 Feature Freeze > > > > Following our discussion on the proposal to push back the feature > > freeze date for 4.2.0 [1], we have not yet achieved a clear consensus. > Well... > > we have already defined the "project rules" for figuring out what to > do. > > In out project by-laws [2], we have defined a "release plan" decision > > as > > follows: > > > > > 3.4.2. Release Plan > > > > > > Defines the timetable and work items for a release. The plan also > > > nominates a Release Manager. > > > > > > A lazy majority of active committers is required for approval. > > > > > > Any active committer or PMC member may call a vote. The vote must > > > occur on a project development mailing list. > > > > And our lazy majority is defined as: > > > > > 3.2.2. Lazy Majority - A lazy majority vote requires 3 binding +1 > > > votes and more binding +1 votes than binding -1 votes. > > > > Our current plan is the starting point, so this VOTE is a vote to > > change the current plan. We require a 72 hour window for this vote, > > so IMO we are in an odd position where the feature freeze date is at > > least extended until Tuesday of next week. > > > > Our current plan of record for 4.2.0 is at [3]. > > > > [1] http://markmail.org/message/vi3nsd2yo763kzua > > [2] http://s.apache.org/csbylaws > > [3] > > https://cwiki.apache.org/confluence/display/CLOUDSTACK/Cloudstack+4.2+ > > Re > > lease > > > > ---------------------------------------------------------------- > > > > I'd like to call a VOTE on the following: > > > > Proposal: Extend the feature freeze date for our 4.2.0 feature release > > from today (2013-05-31) to 2013-06-28. All other dates following the > > feature freeze date in the plan would be pushed out 4 weeks as well. > > > > Please respond with one of the following: > > > > +1 : change the plan as listed above > > +/-0 : no strong opinion, but leaning + or - > > -1 : do not change the plan > > > > This vote will remain open until Tuesday morning US eastern time. > > > > -chip