[openstack-dev] [fuel] Fuel 9.0/Mitaka is now in Feature Freeze

Dmitry Borodaenko dborodaenko at mirantis.com
Fri Mar 4 00:31:56 UTC 2016

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:

Multipath disks, 3/10:

LCM readyness for all deployment tasks, 3/15:

HugePages, 3/16:

Numa, 3/16:

SR-IOV, 3/16:

Decouple Fuel and OpenStack tasks, 3/20:

Remove conflicting openstack module parts, 3/20:

DPDK, 3/24:

Unlock "Settings" Tab, 3/24:

ConfigDB, 3/24:

Osnailyfacter refactoring for Puppet Master compatibility, 3/24:

All other feature changes will have to wait until Soft Code Freeze.

See IRC meeting minutes and log from #fuel-dev for more details:

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

More information about the OpenStack-dev mailing list