Open Stack

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

The Release Candidate (RC) deadline is this Thursday, the 9th. Work should be
focused on any release-critical bugs and wrapping up and remaining feature
work.

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

All cycle-with-milestones and cycle-with-intermediary projects should cut their
stable/rocky branch by the end of the week. This branch will track the Rocky
release.

Once stable/rocky has been created, master will will be ready to switch to
Stein development. While master will no longer be frozen, please prioritize any
work necessary for completing Rocky plans. Please also keep in mind there will
be rocky patches competing with any new Stein work to make it through the gate.

Changes can be merged into stable/rocky as needed if deemed necessary for an
RC2. Once Rocky is released, stable/rocky will also be ready for any stable
point releases. Whether fixing something for another RC, or in preparation of a
future stable release, fixes must be merged to master first, then backported to
stable/rocky.

Actions
-------

cycle-with-milestones deliverables should post an RC1 to openstack/releases
using the version format X.Y.Z.0rc1 along with branch creation from this point.
The deliverable changes should look something like:
    
  releases:
    - projects:
        - hash: 90f3ed251084952b43b89a172895a005182e6970
          repo: openstack/example
      version: 1.0.0.0rc1
branches:
  - name: stable/rocky
    location: 1.0.0.0rc1

Other cycle deliverables (not cycle-with-milestones) will look the same, but
with your normal versioning.

And another reminder, please add what highlights you want for your project team
in the cycle highlights:

http://lists.openstack.org/pipermail/openstack-dev/2017-December/125613.html


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

RC1 deadline: August 9
Stein PTG: September 10-14

-- 
Sean McGinnis (smcginnis)