You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by Chip Childers <ch...@sungard.com> on 2013/06/04 21:35:30 UTC
[VOTE][RESULT] Pushback 4.2.0 Feature Freeze
This vote has *passed* with the following results:
+1 : John, Marcus, Clayton, Ilya, Animesh, Sudha, Min, Will, Alex,
Edison, Kelven, Hiroaki, Abhi, Sateesh, Mice, Kevin, Nitin, Swamy,
Mike (non-binding)
+0 : Prasanna, Koushik
-0 : Chiradeep, Wei, Sebastien
-1 : David, Hugo, Joe
Thank you for taking the time to share your opinions on this topic!
-chip
On Fri, May 31, 2013 at 11:00:21AM -0400, Chip Childers wrote:
> 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+Release
>
> ----------------------------------------------------------------
>
> 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
Re: [VOTE][RESULT] Pushback 4.2.0 Feature Freeze
Posted by Animesh Chaturvedi <an...@citrix.com>.
On Jun 4, 2013, at 4:51 PM, "Chip Childers" <ch...@sungard.com> wrote:
> On Tue, Jun 4, 2013 at 7:34 PM, Animesh Chaturvedi
> <an...@citrix.com> wrote:
>> Also marked the open unresolved bugs for 4.2
>
> If they didn't have a fix version, then why 4.2? What about a 4.1.x
> release or a later 4.2.x release?
Let me clarify I updated the "affects version" with additional tag of 4.2 for bugs that were tagged for 4.1 but not resolved during 4.1.
I did mark few empty fix version as 4.2 but you are right they could as well be for 4.1.1 looks like I will have to check on them again, thanks for calling out
Re: [VOTE][RESULT] Pushback 4.2.0 Feature Freeze
Posted by Chip Childers <ch...@sungard.com>.
On Tue, Jun 4, 2013 at 7:34 PM, Animesh Chaturvedi
<an...@citrix.com> wrote:
> Also marked the open unresolved bugs for 4.2
>
If they didn't have a fix version, then why 4.2? What about a 4.1.x
release or a later 4.2.x release?
RE: [VOTE][RESULT] Pushback 4.2.0 Feature Freeze
Posted by Animesh Chaturvedi <an...@citrix.com>.
Also marked the open unresolved bugs for 4.2
> -----Original Message-----
> From: Animesh Chaturvedi [mailto:animesh.chaturvedi@citrix.com]
> Sent: Tuesday, June 04, 2013 2:52 PM
> To: dev@cloudstack.apache.org
> Subject: RE: [VOTE][RESULT] Pushback 4.2.0 Feature Freeze
>
> I have updated the 4.2 release dates in wiki [1] as a result of the 4
> weeks push out. Please check.
>
> Summary:
> Feature freeze: 6/28
> RC : 8/19
>
> [1]
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Cloudstack+4.2+Re
> lease
>
>
> > -----Original Message-----
> > From: Chip Childers [mailto:chip.childers@sungard.com]
> > Sent: Tuesday, June 04, 2013 12:36 PM
> > To: dev@cloudstack.apache.org
> > Subject: [VOTE][RESULT] Pushback 4.2.0 Feature Freeze
> >
> > This vote has *passed* with the following results:
> >
> > +1 : John, Marcus, Clayton, Ilya, Animesh, Sudha, Min, Will, Alex,
> > Edison, Kelven, Hiroaki, Abhi, Sateesh, Mice, Kevin, Nitin, Swamy,
> > Mike
> > (non-binding)
> >
> > +0 : Prasanna, Koushik
> >
> > -0 : Chiradeep, Wei, Sebastien
> >
> > -1 : David, Hugo, Joe
> >
> >
> > Thank you for taking the time to share your opinions on this topic!
> >
> > -chip
> >
> >
> > On Fri, May 31, 2013 at 11:00:21AM -0400, Chip Childers wrote:
> > > 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+
> > > Release
> > >
> > > ----------------------------------------------------------------
> > >
> > > 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
RE: [VOTE][RESULT] Pushback 4.2.0 Feature Freeze
Posted by Animesh Chaturvedi <an...@citrix.com>.
I have updated the 4.2 release dates in wiki [1] as a result of the 4 weeks push out. Please check.
Summary:
Feature freeze: 6/28
RC : 8/19
[1] https://cwiki.apache.org/confluence/display/CLOUDSTACK/Cloudstack+4.2+Release
> -----Original Message-----
> From: Chip Childers [mailto:chip.childers@sungard.com]
> Sent: Tuesday, June 04, 2013 12:36 PM
> To: dev@cloudstack.apache.org
> Subject: [VOTE][RESULT] Pushback 4.2.0 Feature Freeze
>
> This vote has *passed* with the following results:
>
> +1 : John, Marcus, Clayton, Ilya, Animesh, Sudha, Min, Will, Alex,
> Edison, Kelven, Hiroaki, Abhi, Sateesh, Mice, Kevin, Nitin, Swamy, Mike
> (non-binding)
>
> +0 : Prasanna, Koushik
>
> -0 : Chiradeep, Wei, Sebastien
>
> -1 : David, Hugo, Joe
>
>
> Thank you for taking the time to share your opinions on this topic!
>
> -chip
>
>
> On Fri, May 31, 2013 at 11:00:21AM -0400, Chip Childers wrote:
> > 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+
> > Release
> >
> > ----------------------------------------------------------------
> >
> > 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