Open Stack

Welcome to our regular release countdown email!

Development Focus
-----------------

Focus should be on fixing release-critical bugs in order to produce the
first release candidates (for deliverables following the with-milestones
model) or final Pike releases (for deliverables following the
with-intermediary model), with the R-3 week as a target date (August 10).


General Information
-------------------

For deliverables following the cycle-with-milestones model, we are now
past Feature Freeze. The focus should be on determining and fixing
release-critical bugs. At this stage only bugfixes should be approved
for merging in the master branches: feature work should only be
considered if explicitly granted a Feature Freeze exception by the team
PTL (after a public discussion on the mailing-list).

StringFreeze is now in effect, in order to let the I18N team do the
translation work in good conditions. The StringFreeze is currently soft
(allowing exceptions as long as they are discussed on the mailing-list
and deemed worth the effort). It will become a hard StringFreeze on
August 10.

The requirements repository is also frozen, until all
cycle-with-milestones deliverables have produced a RC1 and have their
stable/pike branches.

Note that deliverables that are not tagged for release by the
appropriate deadline will be reviewed to see if they are still active
enough to stay on the official project list.


Actions
-------

A few cycle-with-milestones deliverables still haven't requested their
Pike-3 tag (X.0.0.0b3): heat networking-bagpipe networking-bgpvpn
networking-midonet networking-odl networking-ovn networking-sfc
neutron-dynamic-routing neutron-fwaas neutron and sahara. If nothing is
proposed by the end of the day, a tag will be forced at the current
master HEAD in order to mark the Feature Freeze.

stable/pike branches should be created soon for all non-already-branched
libraries. You should expect 2-3 changes to be proposed for each: a
.gitreview update, a reno update (skipped for projects not using reno),
and a tox.ini constraints URL update. Please review those in priority so
that the branch can be functional ASAP.

For cycle-with-intermediary deliverables, release liaisons should
consider releasing their latest version, and creating stable/pike
branches from it ASAP.

For cycle-with-milestones deliverables, release liaisons should wait
until R-3 week to create RC1 (to avoid having an RC2 created quickly
after). Review release notes for any missing information, and start
preparing "prelude" release notes as summaries of the content of the
release so that those are merged before the first release candidate.

For release-independent deliverables, release liaisons should check that
their deliverable file includes all the existing releases, so that they
can be properly accounted for in the releases.openstack.org website;

Finally, if you haven't done so already, remember to file Pike goal
completion information, as explained in:

https://governance.openstack.org/tc/goals/index.html#completing-goals


Upcoming Deadlines & Dates
--------------------------

RC1 target deadline (and HardStringFreeze): August 10
Final Pike release: August 30
Queens PTG in Denver: Sept 11-15

As usual come find us on #openstack-release IRC channel if you have any
questions or concerns.

-- 
Thierry Carrez (ttx)