In the past we have unfrozen the requirements repo before it was ideal
to allow changes. In order to make sure the appropriate people are
handling this, updating the PROCESS doc to note that the requirements
team should be the ones to perform this unfreeze.
Change-Id: I7c36be1b6f3f6f0b164901c88f5572d35f05a0c3
The documentation landing page for a series exists as soon as the
series is open, so we can start out the beginning of the cycle with a
releases.o.o page that points to docs.o.o/$series.
Change-Id: Ie2290bce8f36cac6e179e3ce49394cdc7b9c033e
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
The stable-compat jobs are no longer needed, so remove the step saying
to add/update them.
Change-Id: I337bc14129f5e0b5b0d3148b6eb590ad6f9e4d88
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
After the doc-migration, the release team no longer branches the
openstack-manuals repository. They can also establish the new landing
pages for the soon-to-be-open series earlier, and update the series
status for soon-to-be-released series at the same time.
Change-Id: Ide6522e33bdb213eb8d260cea0352e0a014dedb0
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Update instructions about the aclmanager dance between M-2
and M-3, so that we don't repeat the Pike mistakes.
Change-Id: I5a66ac3a67e2a1f5f8eb83f45d5e710545b5ca6c
Relax rules around independent library releases during library freeze
after milestone-3. They may still be released but we'll hold constraint
or requirement changes until after the freeze period.
Change-Id: Idf71f201dc3929ca27789e2a404eb6799c519c5f
In order to reduce no-show risk at library freezes, we'd like to make
sure that we have one library release in the cycle to fall back to.
This is done by asking projects to do at least one library release
before milestone-2. Add corresponding steps to the PROCESS.rst file.
Change-Id: I4f64f931bf944ce5d7a9dfdb99dc458c222b8fcb
We switched to https for docs.openstack.org, adjust most URLs.
This change updates documentation etc files, but not any deliverable files.
Change-Id: Ia8b0524025ab1c685ec6f57246f8b34231f52632
We don't want to send the email until close to the time the press
release will go live.
Change-Id: I862f45c794807125f2046c0f659aec7eb261726f
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Update the release process document to address the issue we ran into
with Ironic this cycle because we didn't encourage them strongly enough
to branch early enough.
Change-Id: Ie864b0e34d9f704dcad7497646117030eb18d1dd
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Instead of requiring the series argument, look at the default that the
rest of the scripts use. There is still a command line option for
overriding the default.
Change-Id: I7168b4786ac8f275da1ff0cd177268b3a4c20c17
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
The aclmanager script needs to be able to get a list of repositories
with the cycle-with-milestone release model, and the data for that lives
in this repository now instead of the governance repository. Rather than
having a tool that relies on this data live in release-tools, move it
here.
Change-Id: I7c2c54c4949829aea92e569e3ac9ec9007d932ed
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Around the time Gerrit ACL changes are prepared, have Infra generate
the next signing key so there's ample time for attestation prior to
its installation at the beginning of the coming development cycle.
Change-Id: I6e3485ce8c3debebcd267826d11e3f44af69a87c
Now that branches can be created on demand, update the process document
to replace the manual instructions with reminders and review
instructions.
Change-Id: I1d8ef79281b937543d9dbf22bf97d7593301f0e9
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Include deadlines in the Ocata schedule and include reminder notes in
the process document.
Change-Id: Ib1fd9961359938b15b567431302d955cdea7ac99
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Move the generation of the patch earlier in the process.
Add a reminder to have PTLs and liaisons +1 the final tag patch.
Change-Id: I486612e79d4f248a9456eac68db25a5cf65f36b6
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Final release process was missing some steps to update the
releases.o.o website (add doc links, mark series released).
Change-Id: I46a64debf32b7ee4817f01eb10779f7bfd22a406
As Tony pointed out, we already have a step to unfreeze requirements
when the milestone projects have branched, so we don't need to repeat
it.
Also clean up a little formatting.
Change-Id: I1675d4af1b285f195bacdd638c49bc42e4829c50
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Provide a link to the newton patch to add bitrot jobs as an example of
what might need to be done for that step in the future.
Change-Id: I50bae0d89b9c15e8ef612a60c6cd73e9e964f114
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Add references to the patches that update the stable compatibility jobs
for newton. Also add the missing step of updating the jobs used by Oslo
to run changes to master against older deployments.
Change-Id: I0bc135a956baa28f0035ce24c258e3fdc2bd24d3
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Add a step to the release process to ensure that the note links are
pointing to the right pages, and update the tool used to do that so it
is more robust.
Change-Id: I7beb85f63212c4ca696c9012b673e4d1b2b6d453
Signed-off-by: Doug Hellmann <doug@doughellmann.com>