Open Stack

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

We are getting close to the end of the Train cycle! Next week on September 12
is the train-3 milestone, also known as feature freeze. It's time to wrap up
feature work in the services and their client libraries, and defer features
that won't make it to the Ussuri cycle.


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

This coming week is the deadline for client libraries: their last feature
release needs to happen before "Client library freeze" on September 12. Only
bugfix releases will be allowed beyond this point.

When requesting those library releases, you can also include the stable/train
branching request with the review (as an example, see the "branches" section
here:

https://opendev.org/openstack/releases/src/branch/master/deliverables/pike/os-brick.yaml#n2)

September 12 is also the deadline for feature work in all OpenStack
deliverables following the cycle-with-rc model. To help those projects produce
a first release candidate in time, only bugfixes should be allowed in the
master branch beyond this point. Any feature work past that deadline has to be
approved by the team PTL.

Finally, feature freeze is also the deadline for submitting a first version of
your cycle-highlights. Cycle highlights are the raw data hat helps shape what
is communicated in press releases and other release activity at the end of the
cycle, avoiding direct contacts from marketing folks. See
https://docs.openstack.org/project-team-guide/release-management.html#cycle-highlights
for more details.


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

Train-3 milestone (feature freeze): September 12 (R-5 week)
RC1 deadline: September 26 (R-3 week)
Train final release: October 16
Forum+PTG at Shanghai summit: November 4