[openstack-dev] [kolla] Mitaka release schedules and priorities - only 30 days left!

Steven Dake (stdake) stdake at cisco.com
Tue Mar 8 23:55:11 UTC 2016

Hi Koala Bears!

The release candidate schedules are as follows:

We are in feature freeze.  No new features in Kolla until after Mitaka is released on April 4th-April 8th.  We may lag this date a little bit depending on the state of the tarballs repo for build from source, or we may just tag and backport when the tarball releases trickle out.

RC1: March 18th: strict tagging deadline!
All blueprints left in the release MUST BE COMPLETED BY THIS DATE
Any remaining feature that was part of a larger blueprint work-item that was highly distributed in nature was converted to an individual Critical priority bug. These mostly involve drop root and reconfigure.  There may be a few other things in there.  Please consider when working on bugs to work the Critical bugs first, then the High bugs, then the Medium bugs, then the Low bugs, then the Wishlist bugs.

RC2: March 25th: strict tagging deadline!
Hopefully all blueprints are in a finished state.  Anything not essential or high in nature will be pushed to Newton.

RC3: April 1st: strict tagging deadline!
This is our final RC unless critical BUGS are found in the implementation.  Missing features will be bumped to newton at this point bug or blueprint wise.  Upgrade is priority #1.  We will branch Mitaka here.

Final release: April 8th: This tagging deadline will be strict assuming other projects hit their deadlines.  I am open to suggestions about how to handle upstream changes in Mitaka past this point.  Master will be open for new features.  ONLY CRITICAL BUG FIXES WILL BE BACKPORTED INTO stable/mitaka.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160308/dfb2d5ac/attachment.html>

More information about the OpenStack-dev mailing list