> -----Original Message----- > From: Chiradeep Vittal [mailto:chiradeep.vit...@citrix.com] > Sent: Tuesday, October 08, 2013 11:21 AM > To: dev@cloudstack.apache.org > Subject: Re: Call for 4.3 and 4.2.1 Release Managers! > > +1. > We should get a call out to the community to see who is expecting to > merge for 4.3. > Although 10/31 is the feature freeze date, proposals and branches > should be in already IMHO. [Animesh>] While I had created and updated the 4.3 page with dates it was not explicitly called out since I was expecting the to-be release manager to state that. We are already passed the feature proposal date of 9/30, does anyone think that the feature proposal last day should be extended to Friday 10/11 giving 72 hour notice. I prefer not to change and stick to the original dates as below.
Feature freeze : 10/31 Code Freeze : 11/29 RC : 12/23 (This is close to Christmas, so either we pull in by couple of days, or make it first week of Jan) https://cwiki.apache.org/confluence/display/CLOUDSTACK/Cloudstack+4.3+Release > > On 10/8/13 9:54 AM, "Chip Childers" <chip.child...@sungard.com> wrote: > > >On Tue, Oct 08, 2013 at 04:49:24PM +0000, Animesh Chaturvedi wrote: > >> > >> > Whomever wants to take the lead for 4.3 should probably (IMO), > >> > start a discussion on (1) coordination of work and > >> [Animesh>] Since we are getting closer to code freeze date and we > >>cannot find overall release management I can pick up 4.3 and call out > >>the roles and ask for volunteers for them. > > > >Sounds good. > > > >> > >> (2) re-thinking the schedule > >> > to reset based on both historic performance and reality of the > >>calendar > >> > (we've really been working on 4.2 when we should have moved on to > >>4.3). > >> [Animesh>] Chip my preference would be to stick to the timeline of > >>4.3 which will make it a smaller release but will give us the > >>opportunity to clear up our technical debt. > > > >+1 to being smaller and tech-debt focused. > > > >-chip
