Open Stack

Focus
-----

Project teams following the cycle-with-milestone model should be
preparing their first Mitaka release candidate this week. The first
release candidate should be tagged (using X.Y.Z.0rc1) as soon as
the pressure to unfreeze master is stronger than the cost of
backporting bugfixes, generally when all known critical bugs have
been fixed. We will create stable branches from the release candidate
tag points.

Project teams following the cycle-with-intermediary model should
ensure they have at least one Mitaka release, and determine whether
they will need another release before the end of the Mitaka cycle.

Any features for which a feature freeze exception was granted but
that haven't landed should be candidates for putting off until
Newton.

All project teams should be working on release-critical bugs.

General Notes
-------------

The global requirements list is frozen. If you need to change a
dependency, for example to include a bug fix in one of our libraries
or an upstream library, please provide enough detail in the change
request to allow the requirements review team to evaluate the change.

User-facing strings are frozen to allow the translation team time
to finish their work.

Release Actions
---------------

We have started creating the stable/mitaka branches for libraries.
Please follow-up to the mailing list thread [1] to acknowledge and
approve the version number to use to create the branch. That list
only includes projects with the release:managed tag, but other
projects can post on the thread to request their own branches.

[1] http://lists.openstack.org/pipermail/openstack-dev/2016-March/088853.html

Important Dates
---------------

Final release candidates: R-1, Mar 28-1
Mitaka final release: Apr 4-8

Mitaka release schedule: http://releases.openstack.org/mitaka/schedule.html