In response to Brocade I see your response "feature should be done (in it's branch) by 19th july. merging and fixing issues may take to mid august" that essentially means feature freeze (cutting the branch) by mid august
Animesh > -----Original Message----- > From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com] > Sent: Wednesday, June 25, 2014 2:07 PM > To: dev@cloudstack.apache.org > Subject: RE: [ACS45][ACS50][PROPOSAL] move forward feature freeze > > I saw you mentioning mid august as well so there is some confusion > > > Animesh > > > -----Original Message----- > > From: Daan Hoogland [mailto:daan.hoogl...@gmail.com] > > Sent: Wednesday, June 25, 2014 1:52 PM > > To: dev > > Subject: Re: [ACS45][ACS50][PROPOSAL] move forward feature freeze > > > > No certainly not, that would mean yet another bigger release and > > another extra shift. It is now at 19 July And I was proposing to move > > it forward to last 19th of june. > > > > On Wed, Jun 25, 2014 at 10:46 PM, Animesh Chaturvedi > > <animesh.chaturv...@citrix.com> wrote: > > > > > > > > >> -----Original Message----- > > >> From: Daan Hoogland [mailto:daan.hoogl...@gmail.com] > > >> Sent: Thursday, May 29, 2014 10:45 AM > > >> To: dev > > >> Subject: Re: [ACS45][ACS50][PROPOSAL] move forward feature freeze > > >> > > >> Seeing what objections there might be I want to amend my proposal > > >> to > > >> > > >> 1. move forward feature freeze not on the coming but on the next > > release. > > > > > > > > > [Animesh] Daan to be clear you are proposing to keep the feature > > > freeze date at Aug 19th > > > > > > > > >> 2. set feature proposal dealine for the coming release on 19th of > > >> June > > >> > > >> flames? other thoughts? > > >> Daan > > >> > > >> On Wed, May 28, 2014 at 8:17 AM, Ritu Sabharwal > > >> <rsabh...@brocade.com> wrote: > > >> > Thanks Daan for the clarification! > > >> > > > >> > -----Original Message----- > > >> > From: Daan Hoogland [mailto:daan.hoogl...@gmail.com] > > >> > Sent: Tuesday, May 27, 2014 1:56 PM > > >> > To: dev > > >> > Subject: Re: [ACS45][ACS50][PROPOSAL] move forward feature > freeze > > >> > > > >> > What I mean is that to prevent the date of oct '14 moving we need > > >> > to > > >> move the feature freeze forward. so we have more time to create the > > >> release. > > >> > > > >> > On Tue, May 27, 2014 at 10:45 PM, Ritu Sabharwal > > >> <rsabh...@brocade.com> wrote: > > >> >> When you say release schedule shift, does it mean 4.5 release > > >> >> target is > > >> moved from Oct '14 to a forward date? > > >> >> > > >> >> Thanks & Regards, > > >> >> Ritu S. > > >> >> > > >> >> -----Original Message----- > > >> >> From: Daan Hoogland [mailto:daan.hoogl...@gmail.com] > > >> >> Sent: Monday, May 26, 2014 5:26 AM > > >> >> To: dev > > >> >> Subject: [ACS45][ACS50][PROPOSAL] move forward feature freeze > > >> >> > > >> >> LS, > > >> >> > > >> >> When I seeing once again our release schedule shift, I think we > > >> >> have no > > >> option but to move feature freeze for the next release forward. > > >> >> This is the only way it seems we can reduce the complexity of > > >> >> the total > > >> sum of changes. Therefore it is the only way we can prevent lapsing > > >> even more in time without risking reduced quality of our next release. > > >> >> So I propose to move feature freeze forward by a month to be at > > >> >> the > > >> 19th of June (instead of July). I don't think we need to strictly > > >> move code freeze forward as well but vigilance onto added features > > >> will > > be necessary. > > >> >> > > >> >> -- > > >> >> Daan > > >> > > > >> > > > >> > > > >> > -- > > >> > Daan > > >> > > >> > > >> > > >> -- > > >> Daan > > > > > > > > -- > > Daan
