96 Commits

Author SHA1 Message Date
Sean McGinnis
355cd7debd
Add script to semi-automate bulk releases
The release team has a few cases now where we need to propose release
patches for a large set of deliverables. Due to differences in semver
choice based on actually merged commits, along with other decisions that
need to be made while doing these, this process can't be completely
automated. But this adds a script that will automate the majority of the
process to simplify it as much as possible.

Change-Id: I6ec9fa77baab58df93bdadc0ac3c3fa5d3e18804
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
2020-09-11 14:48:55 -05:00
Sean McGinnis
d52db3353e
Update devstack-gate update instructions
Devstack-gate has been restructured since we added references to patches
to show what needs to be done to prepare for new stable branches. This
is a trivial update to point to a more recent review that is a better
example of what needs to be done.

Change-Id: Iacffaf3dce12b3aaea113d057d497e19970d0fc2
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
2020-08-27 11:43:10 -05:00
Sean McGinnis
d593479b0b
Test bugfix branching with release-test
This does a new release with release-test to see if everything is
covered to allow branches to have a bugfix/* prefix.

Change-Id: I7869cf412524d7352249f02f7449b2fddf401d2c
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
2020-06-29 15:40:12 -05:00
Zuul
c239b4c4fb Merge "Move the "Adding a deliverable" section" 2020-06-19 16:06:04 +00:00
Thierry Carrez
de89086844 Move the "Adding a deliverable" section
Information about adding a deliverable should live in the
general usage documentation, not the release models page.

Also stop advising projects to release independently if they
get added after the second milestone of a series, as it creates
issues down the road with inconsistent stale pages in the
'Independent' section.

Change-Id: I9319656b62b063d637737ad8667d3099f179fb58
2020-06-17 16:33:51 +02:00
Thierry Carrez
309e95eaad cycle-automatic is just stable-branch-type: none
Now that releases are systematically proposed for deliverables with
changes at the end of a cycle, the cycle-automatic release model is
really better described with cycle-with-intermediary combined with
the 'stable-branch-type: none' option.

Change-Id: Ia9c5dadcaa89fbbdb7420a52cc3fed665e4ba513
2020-06-16 17:33:02 +02:00
Thierry Carrez
8a9f755cb9 Trailing is a deliverable type, not a release model
Cycle-trailing deliverables are regular cycle-following deliverables,
using RCs or not not using RCs -- they just have a different deadline.

Rather than using a release model, those deadline variants are better
described using deliverable types, in much the same way 'library'
deliverables have a specific deadline too.

This simplifies the list of models significantly, and allows to have
proposer validation of trailing deliverables that use RCs or not use
RCs.

For compatibility in old branches, setting 'cycle-trailing' is still
supported, it will just overload the type to 'trailing' if specified.

Change-Id: Ifce88ef3e5dd406f45f25214699f16e736ad5377
2020-06-16 16:18:30 +02:00
Sean McGinnis
804e560832
Add std-with-versions stable-branch-type
This adds a new std-with-versions branch type. This is used to control
validation logic when branching to allow the Ironic team to create
intermediary stable branches based on major.minor version numbers in
addition to our normal expected stable/$series branches.

https://specs.openstack.org/openstack/ironic-specs/specs/not-implemented/new-release-model.html

Change-Id: Ic482c77a2c177162ffe37643a455ac1724a658b3
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
2020-06-02 14:34:32 -05:00
Zuul
0a18586488 Merge "Add some branch prep steps to the process doc" 2020-05-27 11:47:38 +00:00
Sean McGinnis
15f8434060
Update release week process
Change-Id: I07fc80284a955be93b9841d6affcfaa285cd65ee
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
2020-05-13 07:37:22 -05:00
Hervé Beraud
c734adc29d [doc] R1 3rd point - Testing the Final Release Plumbing
Change-Id: I0cbcb1d857d7b9e11d4e0c07d09e77cbb2e76a1b
2020-05-05 16:29:39 +02:00
Hervé Beraud
c3ba3e2bad add useful links for R-2 3rd step is doc
Change-Id: I0385a3cbcc1cf771c9f3b7caef11ee46463514a6
2020-04-29 15:34:25 +02:00
Hervé Beraud
5f5fbb01b5 [doc][process R-2] clarifying our role
Change-Id: Ib5c585913bff52703b68256cc74e6792ca4d9544
2020-04-29 15:33:35 +02:00
Hervé Beraud
cba253fb89 add doc related to R-2 and requirements update
Change-Id: Iba475c5ea09077c438238b7ad6e0b5046987dfc9
2020-04-28 18:38:40 +02:00
Hervé Beraud
6289d89bc8 add some doc about process on R-2
Change-Id: I104c07bce2e8a36c725acc8f5616898bd1a280b0
2020-04-28 16:05:28 +02:00
Zuul
bdfe3dee95 Merge "add an example on release notes instructions" 2020-04-28 13:59:56 +00:00
Zuul
34be255899 Merge "Expand on release notes instructions" 2020-04-28 13:56:50 +00:00
Sean McGinnis
b6ea747a67
Add some branch prep steps to the process doc
This adds some steps to be done as we near the end of a development
cycle to make sure we are ready when stable branches are created.

Change-Id: I56ae71a6d9869ab138c256d9d3021dfd8fd1402e
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
2020-04-27 16:52:37 -05:00
Hervé Beraud
b69dd4e78a add an example on release notes instructions
Change-Id: I84df667ea972b5a55f4d63b6dda8c9be7d439791
2020-04-27 17:36:12 +02:00
Hervé Beraud
3853711a2c Add doc related to ./tools/add_release_note_links.sh
Change-Id: Ic2bbe41c7e66e7d81ed177ee8dc94796aba0d3e8
2020-04-27 16:45:46 +02:00
Sean McGinnis
c3ab362be5
Expand on release notes instructions
Change-Id: Id43ba73198a04d9e4b6eef27bb2aca4467609455
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
2020-04-27 09:05:32 -05:00
Sean McGinnis
a7a5ad2a94
Add script for adding PTL and liaisons to reviews
This adds a script that will go through all release reviews under a
given review topic, find the PTL and release liaisons for the owning
teams of those releases, and add them as reviewers to the patch.

Change-Id: I6294c1d9da7d6a977df6d8460aa085d2cc7e72a5
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
2020-04-23 07:40:58 -05:00
Sean McGinnis
2e9d9caf4a
Add details to unreleased lib check
Change-Id: Ia232a4344fbecd124229101f4e0ec88b88910073
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
2020-04-10 09:24:17 -05:00
Thierry Carrez
0ada281623 Fix formatting issues in R-2 week
Wrong indent resulted in formatting issues in the HTML rendering.

Change-Id: I325f42d64cb0d9f1b16d4f7957d975feeca3b897
2020-04-09 12:28:39 +02:00
Thierry Carrez
e9a7decec2 Update milestone2-to-milestone3 process
Update process based on tasks we did between ussuri-2 and ussuri-3.

Change-Id: I52f34b3ad81aa9197bf124505bccfcb16fd67f25
2020-04-02 18:08:20 +02:00
Thierry Carrez
3c0c72be8f Use governance_consistency.py for MembershipFreeze
The new governance_consistency.py tool lists all inconsistencies
between deliverables defined in openstack/releases and deliverables
defined in openstack/governance. Using it instead of the
membership_freeze_test tool (which only listed deliverables defined
in governance that did not have a corresponding deliverable file)
gives us the chance to fix all inconsistencies before milestone-2.

Change-Id: I34c2454082054b6e49edf16784e0e9213799ecc1
2020-03-25 11:09:18 +00:00
Sean McGinnis
7ce6f9bda6
Clarify tarball-base schema use
Change-Id: I541c5f78c038733c5d96928ec44a92f903cbb1fb
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
2020-02-20 16:46:40 -06:00
Zuul
b79a0c054c Merge "Fix schedule generation instructions" 2020-02-20 16:33:30 +00:00
Thierry Carrez
f24fbcbee5 Update process with weekly email content
Now that ussuri-2 is past us, update the process to add
weekly email content that was posted during those weeks.

Change-Id: I738a1678e7a236ce8fb30de25978bac6a2db680a
2020-02-18 15:03:31 +01:00
Sean McGinnis
13c2870029
Fix schedule generation instructions
Change-Id: Iebbd751f0e25364cd35f3153cc908911b8c062e9
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
2020-02-14 11:18:11 -06:00
Thierry Carrez
80a0616359 Skip sig links if the skipped-sig flag is set
In releases.o.o we display signature links for all deliverables,
if the series is > Ocata or independent. Since some "independent"
deliverables predate the signature generation tooling, that results
in a number of "independent" deliverables displaying broken signature
links, which makes us look bad.

This adds a flag (skipped-sig) that can be set for independent
deliverables that did not have any signature generated (pre-Ocata), and
skips the signature link display if the flag is set.

As a practical example, this fixes broken links for PBR<2. Tony signed
up to automatically generate the others.

Change-Id: I44a49e3f08010a85c64673d2292528139eabcc99
2020-02-05 18:31:44 +01:00
Tony Breeds
c582feffc0 Add docs for tools/make_missing_releases.sh
Change-Id: I83e64de23ae75f5abedc6219a07a8cfdd661687d
2020-01-23 12:29:33 +00:00
Tony Breeds
60e786d724 Add tools/bulk_review.sh and get-contacts
get-contacts:
To extract the PTL/Liaison contact information from the governance data
/ release team data

tools/bulk_review.sh:
To manipulate a dirty working-tree and post as a single gerrit topic,
one change per team.  Changes are unordered so any change can be merged
when it's ready/ approved by the appropriate team

Also enhance get-deliverable-owner: to detect file paths

Story: 2005704
Task: 31028

Change-Id: Ia319e8a7b4da195cb4bc861c51025a41adc43bb3
2020-01-23 11:52:59 +00:00
Thierry Carrez
5a65463fd1 Update process for between milestone-1 and 2
Refresh process based on what was done on week R-18.

Change-Id: I6f8f3333fd18f6cc472aba6697d47a6e86f16ba8
2020-01-10 12:39:52 +01:00
Zuul
f225321d0d Merge "Add command to list cycle-trailing to process" 2020-01-09 20:22:51 +00:00
Zuul
7f4cc0edf5 Merge "Introduce 'abandoned' release model" 2020-01-09 18:03:03 +00:00
Zuul
2f703a25fb Merge "Fix propose-update-constraints job name in docs" 2019-12-19 10:20:38 +00:00
Thierry Carrez
655b62e84c Introduce 'abandoned' release model
Introduce an 'abandoned' release model for cycle-independent
deliverables. It should only be applied to deliverables in the
_independent directory. No new release should be accepted for
deliverables with this release-model.

Change-Id: I65c163888c37f7a7f77273abf3ca0633923a0fe2
2019-12-18 17:57:06 +01:00
Thierry Carrez
b2a90e3f91 Update process for ussuri-1 weeks
Update process based on what happened in the weeks before and after
ussuri-1.

NB: actions around governance/releases consistency checks will be added
later, when the tool is ready and standing issues are resolved.

Change-Id: I046fd116c8d91bb6707855c9ba489b8d5791b45b
2019-12-18 15:06:37 +01:00
Sean McGinnis
9637356133
Fix propose-update-constraints job name in docs
The propose-update-constraints job was referred to as
propose-upper-constraints. Update name to make it a little easier if
someone is looking for references to the actual job.

Change-Id: I707b2a498af491c9d2e481ed1880ad74839c9389
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
2019-12-16 13:53:52 -06:00
Sean McGinnis
1859b1d4ba
Add command to list cycle-trailing to process
Change-Id: I0a5313c92d38616cec146b1654b54ffd56cb0cf1
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
2019-12-05 11:11:02 -06:00
Thierry Carrez
09e8ffb3b1 Introduce tool to check PTL/liaison approval
This is the first step into automating PTL/liaison approval.
This tool will check that PTL/liaisons either authored the change or
approved it.

Change-Id: I1bbb371997e9e92f39eff47adb4d3d176af35de7
2019-12-05 17:35:06 +01:00
Thierry Carrez
f33b0d3358 Update process for R+1 week
Move R+1 week process items to the top of the document, remove obsolete
steps and merge the remaning ones with pre-PTG steps. Include weekly
email content. Move the step about proposing a schedule for the next
release to "between m-2 and m-3", as this is when we actually do that.

Change-Id: I5a4a7e5e059156139944a09e4d7813bd11ec1c5a
2019-11-14 14:47:50 +01:00
Sean McGinnis
10dfcb1621
Update process with new liaison tracking info
This updates the instructions in the process document to point at the
new home in the data files rather than the old wiki location.

Change-Id: I68a25d80edfc933ff9685846ad62f194a19c4043
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
2019-10-28 10:31:01 -05:00
Thierry Carrez
58be973669 Update release process for R-1 and R+0
Refine process based on what happened in R-1 for Train,
and adjust process based on what is planned for R+0

Include the template for the R+0 release weekly email.

Change-Id: Iabb57b47a5ec37248733526c709d7011636df414
2019-10-10 12:36:01 +02:00
Thierry Carrez
2e661ef351 Update process for R-3, R-2 and R-1 weeks
Further refine release process tasks for R-3, R-2 and R-1 weeks.

Change-Id: I118760bc31440457a415f5c8248f6ff94493255f
2019-10-08 14:10:38 +02:00
Thierry Carrez
c39bd57875 Turn process into week-actionable items
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
2019-10-08 14:10:38 +02:00
Zuul
ba86152af3 Merge "Clarify release-test purpose" 2019-10-07 14:24:36 +00:00
Witek Bedyk
02b6945641 Fix command-line options formatting
To render command-line options correctly, they should be quoted in
double backticks. This change fixes formatting for `new-release` command
options.

Change-Id: Iebbd2994d5ded61beb9f308656b7779482ce9d16
2019-09-30 12:37:51 +02:00
Jean-Philippe Evrard
a0e9fb4381 Clarify release-test purpose
This is not clear what release-test is for.

I expected the repo to be used for final release, as a canary
test. I expected things had to done with it beforehand.
But I only got a confirmation through IRC (as this is not yet documented
in the process), that it only serves during RC/final release time.

This should clarify it.

Change-Id: I9ba636a8a3147466a1e661c074a050ff14a6d394
2019-09-20 15:17:27 +00:00