The release team involvement ladder and infrastructure primer were
hard to find in CONTRIBUTING.rst. It's better to move them next to
the rest of the team documentation.
Change-Id: I3859ce431711cef5176a3ea34b9433bd06d51447
This sets the end date for the Wallaby key, adds the Xena key
starting today and links to a minimal export of the corresponding
public key and its details on the keyserver network.
Change-Id: I012696f62c41915b71dfc12f3c658decc26e9644
Branching the devstack-plugin-* is missing since 2 cycles
(victoria/wallaby), these changes add a related task at R-3 to
ensure to not miss them anymore.
Some tasks of R-2 aren't crystal clear about the expected state of the
series branching.
Some commands are more or less duplicated and inefficient.
Indeed, the QA PTL should be "reminded" once branching is done but the
checks are made after. Also we previous version of this doc was using
two commands who are more or less similar, however, one of them doesn't
caught the `cycle-with-intermediary` deliverables and also doesn't ignore
trailing projects (branching isn't mandatory at this point for them).
These changes remove the duplicated commands and prefer to use the
better one.
These changes reorder steps to "remind" people at the right time and when
all prerequisite are there.
Change-Id: I765e74b15e1f8fc6e45fb90662d04464faf17640
Previously the tempest plugins were driven by the legacy
`cycle-automatic` model. However this model have been abandoned.
The cycle-automatic release model is now better described by the
`cycle-with-intermediary` model combined with `stable-branch-type: none`
The `cycle-automatic` model was used by specific technical deliverables
that needed to be automatically released once at the end of a cycle.
the tempest-plugin are branchless and `cycle-with-intermediary`
however our process doesn't handle them at the end of the cycle
like did the `cycle-automatic`.
These changes clarifying that point.
Change-Id: I6b3619a44d0aea1fa4852e650cbafcb08c853353
The Wallaby and Xena release highlights document is still referring
to the OpenStack Foundation. This patch changes that to Open
Infrastructure Foundation.
Signed-off-by: Ildiko Vancsa <ildiko.vancsa@gmail.com>
Change-Id: I5eb4e67123d1fbb863c70ca29333568c464370af
Some traiing projects follow the cycle-with-rc model however our doc
and our tools doesn't differentiate them during RC1. These project
doesn't have to be released during RC1. These changes adapt our process
accordingly.
Change-Id: I44040bc040f19a75c468d385395323fe0a1f459a
These changes aim to standardize the gerrit topic to use with on our patches.
This:
- will allow us to better retrieve the history from previous series;
- could allow us to generate some statistic and monitoring from series
to series to allow us to get a better big picture of things are.
I already defined this point the potential process/tools changes for Xena.
https://etherpad.opendev.org/p/xena-ptg-os-relmgt
Maintenance mode is becoming more and more prominent, a little standardization
can't hurt.
Change-Id: Ib7ea93fce7e618a2dbba8dd9f4153897bdfee22a
The process was a bit unclear on what to do with libraries that
did not have changes / releases in the current cycle but still
should not be transitioned to "independent" (like client libraries
and other libraries that should stay attached to their main
deliverables release model).
Change-Id: I4ee317c71f90d2f502d3852d8499752dc39177eb
With the new option of the script (delete a branch) the documentation
is updated to express this as well.
Change-Id: I9445b4f8abff81c11a397a15a85cb1ffe1e5bfec
This tool will be used in doc addition around the branching period
to ensure that we don't miss to create stable branches for project.
Also this tooling should be used around each trailing deadline to ensure
to not forget a trailing projects. Trailing projects are those who can
easily meet the conditions that lead to forget to branch them.
Adding usage of this tooling in our process to ensure to check that
point once a time at each new series.
Change-Id: I2a8bd25ecfe5bb1bde5af16b08f897a5bdc11cb7
Add code and spec submission deadlines that the manila
project maintainers adhere to.
Change-Id: I58200d7b12c3a3cda7166da965619016d97f71ea
Signed-off-by: Douglas Viroel <viroel@gmail.com>
The doc is outdated and `list_library_unreleased_changes.sh` produce a
list of changes that can't be consumed directly by `process_auto_release`.
`list_library_unreleased_changes` should be updated to only provide
pojects name. `process_auto_release` already provide list of diff so we
don't need to duplicate that.
Also fixing a wrong command name.
Change-Id: I59e4adaf19095ec0569bf86ddf1e4b99f440dda2
