Open Stack

Based on the list of approved exceptions, we're going to be merging some
feature changes until March 24. It doesn't make sense to have Soft Code
Freeze until a couple of weeks after that, so I propose to shift the
release dates by 3 weeks:

9.0 Soft Code Freeze: April 6
9.0 Release: April 20

Updated schedule:
https://wiki.openstack.org/wiki/Fuel/9.0_Release_Schedule

-- 
Dmitry Borodaenko


On Thu, Mar 03, 2016 at 04:31:56PM -0800, Dmitry Borodaenko wrote:
> Following feature freeze exceptions were granted, ordered by their merge
> deadline. See linked emails for additonal conditions attached to some of
> these exceptions.
> 
> UCA, 3/10:
> http://lists.openstack.org/pipermail/openstack-dev/2016-March/088309.html
> 
> Multipath disks, 3/10:
> http://lists.openstack.org/pipermail/openstack-dev/2016-March/088282.html
> 
> LCM readyness for all deployment tasks, 3/15:
> http://lists.openstack.org/pipermail/openstack-dev/2016-March/088310.html
> 
> HugePages, 3/16:
> http://lists.openstack.org/pipermail/openstack-dev/2016-March/088292.html
> 
> Numa, 3/16:
> http://lists.openstack.org/pipermail/openstack-dev/2016-March/088292.html
> 
> SR-IOV, 3/16:
> http://lists.openstack.org/pipermail/openstack-dev/2016-March/088307.html
> 
> Decouple Fuel and OpenStack tasks, 3/20:
> http://lists.openstack.org/pipermail/openstack-dev/2016-March/088297.html
> 
> Remove conflicting openstack module parts, 3/20:
> http://lists.openstack.org/pipermail/openstack-dev/2016-March/088298.html
> 
> DPDK, 3/24:
> http://lists.openstack.org/pipermail/openstack-dev/2016-March/088291.html
> 
> Unlock "Settings" Tab, 3/24:
> http://lists.openstack.org/pipermail/openstack-dev/2016-March/088305.html
> 
> ConfigDB, 3/24:
> http://lists.openstack.org/pipermail/openstack-dev/2016-March/088279.html
> 
> Osnailyfacter refactoring for Puppet Master compatibility, 3/24:
> http://lists.openstack.org/pipermail/openstack-dev/2016-March/088308.html
> 
> All other feature changes will have to wait until Soft Code Freeze.
> 
> See IRC meeting minutes and log from #fuel-dev for more details:
> http://eavesdrop.openstack.org/meetings/fuel/2016/fuel.2016-03-03-16.00.html
> http://irclog.perlgeek.de/fuel-dev/2016-03-03#i_12133112
> 
> -- 
> Dmitry Borodaenko
> 
> 
> On Wed, Mar 02, 2016 at 10:31:09PM -0800, Dmitry Borodaenko wrote:
> > Feature Freeze [0] for Fuel 9.0/Mitaka is now in effect. From this
> > moment and until stable/mitaka branch is created at Soft Code Freeze,
> > please do not merge feature related changes that have not received a
> > feature freeze exception.
> > 
> > [0] https://wiki.openstack.org/wiki/FeatureFreeze
> > 
> > We will discuss all outstanding feature freeze exception requests in our
> > weekly IRC meeting tomorrow [1]. If that discussion takes longer than
> > the 1 hour time slot we have booked on #openstack-meeting-alt, we'll
> > move the discussion to #fuel-dev and finish it there.
> > 
> > [1] https://etherpad.openstack.org/p/fuel-weekly-meeting-agenda
> > 
> > The list of exceptions requested so far is exceedingly long and it is
> > likely that most of these exceptions will be rejected. If you want your
> > exception to be approved, please have the following information ready
> > for the meeting:
> > 
> > 1) Link to design spec in fuel-specs, spec review status;
> > 
> > 2) Links to all outstanding commits for the feature;
> > 
> > 3) Dependencies between your change and other features: what will be
> > broken or useless if your change is not merged, what else has to be
> > merged for your change to work;
> > 
> > 4) Analysis of impact and risks mitigation plan: which components are
> > affected by the change, what can break, how can impact be verified, how
> > can the change be isolated;
> > 
> > 5) Status of test coverage: what can be tested, what's covered by
> > automated tests, what's been tested so far (with links to test results).
> > 
> > -- 
> > Dmitry Borodaenko