[openstack-dev] [PTL][release] Reminders for Queens-3 January 25

Sean McGinnis sean.mcginnis at gmx.com
Wed Jan 24 17:41:57 UTC 2018

Hey everyone,

The queens-3 milestone is tomorrow. This is a big week for deadlines as this is
also official Feature Freeze, the final release date for client libraries, the
start of soft string freeze, and the beginning of the requirements freeze.

Please make sure all release requests are submitting some time before the end
of tomorrow.

As everyone prepares to do these release patches, I just wanted to point out a
few things to keep in mind.

Client Branching

Since this is the freeze for all clients, please include the creation of the
stable/queens branch with these requests.

As a reminder, the way this works is to add a "branches" section to the
deliverable yaml file. So if you are doing a 1.0.0 release like so:

  - projects:
      - hash: 90f3ed251084952b43b89a172895a005182e6970
        repo: openstack/example
    version: 1.0.0

You would then include the following to create the branch from that point:

  - name: stable/queens
    location: 1.0.0

Release Notes Link

If your repo includes release notes and you would like them to show up on the
releases page [1], the deliverables yaml file will need to include the URL for
those notes:

release-notes: https://docs.openstack.org/releasenotes/example/unreleased.html

Note however that this is currently "unreleased" in the URL. You can do this
now if you want to get current release notes out there, but it may be better to
wait until RC when unreleased.html can be changed to queens.html

[1] https://releases.openstack.org/queens/index.html

Cycle Highlights

We will want this be RC, but you can start adding cycle highlights for your
team already if you wish. If you already know of some highlights from queens
that you will want published, those can be added at any time and will get
included in the generated output.

As a reminder, details of the new release highlights mechanism can be found


New_Release Tool

And one final reminder in case it's useful to you - we have a tool in the
releases repo that helps generate the deliverable yaml file:


You can run this by calling:

tools/new_release.sh queens python-cinderclient feature --stable-branch

That should update the deliverable file with an increment release number based
on the type ("feature" in this case, so the Y in X.Y.Z) and include the stable
branch creation pieces.

Any questions about any of this, please feel free to ping us in the
#openstack-release channel.


Sean McGinnis (smcginnis)

More information about the OpenStack-dev mailing list