Comment 55 for bug 1823200

Here's what I think about the ordering of this. We want there to be as little time between steps as possible.

(0) Make https://bugs.launchpad.net/cinder/+bug/1823200 public.

(1) Propose all os-brick patches, even ussuri. If you rebase before pushing the patches, we won't need merge commits, and I can get the release patches ready sooner. Don't forget to include the release note for each branch (attached to the Launchpad bug) and "Closes-bug: #1823200" in the commit message.

(2) Also propose the cinder patches. Include the release note and "Closes-bug" as above. We won't be able to merge them yet because they won't pass Dell-EMC CI until we update the requirements.txt and lower-constraints.txt (which we can't do until the new os-brick releases happen).

(3) Once all patches are posted, I'll update the OSSN with the gerrit urls, put up a security-doc patch, and update the OSSN in the wiki. Even if the patches haven't merged yet, they will be available for operators to look at and start planning. So I guess at this point I also send the OSSN to openstack-discuss and openstack-announce?

(4) I'll post release patches for all os-brick branches as soon as the patches in (1) have merged.

(5) The release patches will trigger an upper-constraints update. We can ask Sean to line up another requirements person in addition to himself to approve those patches. (We won't be able to merge the cinder change in any branch until the upper-constraints has changed, but at least the patches will be available.)

(6) Update the requirements.txt and lower-constraints.txt in each of (2). (I'm thinking that I'll probably do this because it will be late in UTC+3 at this point, but we can work that out.) I'll have to line up two other people in cinder coresec to approve.

(7) After all (6) have merged, I'll propose cinder releases.

And I think that's it?