It took a non-trivial amount of effort to turn our process into
actionable items for every week of our team tracker. Start
reformatting R-6 to R-4 based on what we just did for Train.
Change-Id: I53189c838875836d030062fa1fd71ba7f0ae1eff
All releases are announced to the release-announce ML, except
Release candidates, which were still sent to openstack-discuss.
The rationale was that RCs should be announced to a developers
list rather than a downstream consumers list, so that they trigger
testing. But that is less true now that there is a single -discuss
list, where they generate a lot of noise around RC1, without
triggering any additional testing. They also confuse some downstream
consumers which expect those to go to the usual release announce list.
This patch removes the exception and makes sure we send all RC
announces to the release-announce list.
Change-Id: Id33dba37b4d53962a2170ec401499fe3dd2e24bf
puppet-openstack-integration holds some of the CI configs and the spec
helper is also needed for CI related things
Change-Id: I7827fc6f317d69c0828fd42b54cb81ca237c5cfb
This commit cut the train branch for grenade
Next step will be on grenade and devstack-gate side to complete
the step 9 mentioned in https://releases.openstack.org/reference/process.html#rc1-week
Change-Id: I66085d37d8a602cc7163dccef9ced8f737f94474
If we make Ussuri the future release, the htaccess will be generated
with redirections for it. When we decide that Train is maintained and
not developed, we should move Ussuri to development. And add 'Vancouver'
or something when we know the next series name to immediately generate
the new redirection.
Alternatively, we could change the code to generate the redirections
at all times. If the code is idempotent, we would never have an
issue of "forgotten" state of a series, and could bypass it.
Change-Id: I69008ebd330a90ae42166d55e5c06b694fc2d042
because rc1 was missing the release note for 4.0.0
the new hash for rc2 includes the release note change.
Change-Id: I51bffb9109b6b874aef660932b7bfba87ac5c2ab