Comment 42 for bug 1823200

Brian: Basically whatever time you, Ivan and Sean are comfortable doing it should be fine. Just switch this bug from Private Security to Public first and add the "security" bugtag to it. That way if you include a Closes-Bug: #1823200 as a commit message footer for the various changes, this bug and the security ML should get updated automatically with links to them. I've marked the OSSN project as affected to it will get a bugtask, and assigned it to you. I recommend pushing the security-doc change around the same time as the cinder/os-brick changes. Your plan in comment #40 looks great, though if there is no convenient time overlap between you and Ivan, some delay between those is likely fine too. I probably wouldn't send the announcement about it to the ML until the related changes merge to affected branches you're listing, since interested parties may take that as a queue to pull updated branches immediately to obtain those patches.