I propose that we also set a date for contributors to claim features and also a date for contributors to indicate risk level.
For example, I see quite a few improvements and features that are unassigned. Past a certain date if they're not claimed, we should be able to say this won't make it into the release. --Alex > -----Original Message----- > From: Chip Childers [mailto:chip.child...@sungard.com] > Sent: Wednesday, December 19, 2012 8:57 AM > To: cloudstack-dev@incubator.apache.org > Subject: [ACS41] Schedule Reminder - Feature freeze on 2013-01-31 > > Hi all, > > I wanted to remind everyone about the schedule for getting new > features and improvements integrated into master. > > The window closes on 2013-01-31, and the general consensus has been > that the features should be complete, come with tests and at least > have draft documentation. > > The list of features and improvements that have been tagged in Jira as > targeting 4.1 are on the release wiki page [1]. If you are working on > something that isn't in that list, then please do create / update the > appropriate records in Jira. This will help as we look to review the > status more frequently during the month of January. > > Thanks! > > -chip
