101 Commits

Author SHA1 Message Date
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
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
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
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
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
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
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
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
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
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
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
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
Sean McGinnis
73d6e8b1a0
Update lib release instructions for freeze
This updates the instructions for client and non-client lib freeze to
make sure all changes are captured in a final release. Also adds a
helper tool to separate out the two types of libs since they have
different deadlines.

Change-Id: I29ea73bcc5a9649d7d9c502ebc0a05c840e41484
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
2019-09-19 16:04:06 -05:00
Sean McGinnis
ef31f7a022
Improve cycle end/beginning process documentation
There were some inaccuracies and some missing information for some of
the tasks to be performed between cycles.

Change-Id: I48af839c200b316c28185cd992a83c996dd740e4
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
2019-09-16 13:26:32 -05:00
Thierry Carrez
0e9086ae98 cycle-with-intermediary release process details
Relax release process for cycle-with-intermediary deliverables,
while still ensuring that:

- they are encouraged to release multiple times
- they are encouraged to switch to cycle-with-rcs if they
  routinely only release once
- they are released at least once before RC1

Change-Id: I2c49559f113f938dfaefd925d5fcc49d60da5828
2019-08-09 12:02:20 +02:00
Thierry Carrez
845e10c092 List deliverables not released since given date
Allow list_deliverables to filter output to list only deliverables
that have not been released since a given date (--unreleased-since).

This will be useful to compile list of libraries to autorelease at
milestones, or check for cycle-with-intermediary services that may
need a refresh release.

Additionally, if --show-dates is provided, the dates for last releases
(or all releases if -a option is provided) will be retrieved (and
displayed if in verbose mode).

Retrieving release dates is done through querying opendev's API for
tag references and looking at committer dates, so it requires Internet
access and increases command run time. It is only enabled if
--show_dates or --unreleased-since are enabled.

Task: 35684
Change-Id: I00aff6703e85a00572edb363973c92b883a79456
2019-07-11 10:45:08 +02:00
Thierry Carrez
b0f8d79dc0 Introduce cycle-automatic release model
For things like tempest-plugins, the cycle-with-intermediary model
is a bit overkill, especially now that we encourage multiple
intermediary releases to qualify.

Introduce a new 'cycle-automatic' model for deliverables that only
need to be released once, automatically at the end of the cycle.
This is limited to "other" or "tempest-plugin" deliverables.

Task: 31025
Change-Id: I83ff63cef18ae297013c3761a373078e580cf58b
2019-06-20 15:54:57 +00:00
melissaml
e700061762 Rename review.openstack.org to review.opendev.org
There are many references to review.openstack.org, and while the
redirect should work, we can also go ahead and fix them.

Change-Id: I0d46b1a4e00c1775ea5e38d39e87bed99f6bbb2e
2019-05-12 04:33:25 +08:00
Sean McGinnis
804df78394
Update cycle process based on PTG review
This updates our process guide to incorporate the updates and changes we
identified while going through all steps during the Denver PTG.

Change-Id: Ib91bea5f874880f37d4d0e90c111ae0b89efa9d4
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
2019-05-06 13:31:24 -05:00
Doug Hellmann
915a9a9d33 add a tool to show changes in rc-based repos
Simplify the instructions by providing a special script and then
update the instructions to refer to it.

Change-Id: Ibbcd422c06dc4aeb3df503f3c0f084b39d3bf0f7
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
2019-03-27 13:54:24 -04:00
Sean McGinnis
f5c1e1a6b7
Add init-series info to process document
This adds instructions to our process document on how to prepare for the
next release cycle once the current one is complete.

Change-Id: I6f958facbfd7043a565ca5c2c0dcbfd6b3d54ad5
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
2019-03-22 15:09:44 -05:00
Thierry Carrez
038e855fb1 Reorder steps on RC1 week process
For RC1 week the steps are roughly in chronological order.
In order to get cycle-highlights in time for the deadline,
move that point up.

Change-Id: I40fd38599b0851dd596f9669edd8d26ccedd8c2a
2019-03-14 17:50:22 +01:00
Zuul
7f7ad24dc3 Merge "Update process with command line instruction" 2019-02-27 02:58:29 +00:00
Jean-Philippe Evrard
d4bab173f2 Update process with command line instruction
This is the first step to complete the process which doesn't hold
the whole series of tools available at our disposition in the repo.

Change-Id: I6468fb176d85d0b79cccf6746b8af7a127217b00
2019-02-26 22:48:44 +00:00
Kendall Nelson
e073100963 Add Cycle-Highlights to process.rst
Cycle highlights are now a regular part of a release and should
be included in the process document so we can promote and
collect them in a routine manner.

Change-Id: I025c029469e3fae85485b87351da9ec487ff5c89
2019-02-14 11:43:37 -06:00
Thierry Carrez
cec56b4c6d Update process to account for Stein changes
During the Stein cycle we introduced three process changes:

- no longer forcing releases around milestones for
  cycle-with-milestones deliverables, and autogenerating RC1
  release requests [0]

- triggering releases for libraries at every milestone if
  they had changes that were not otherwise released since
  the previous milestone [1]

- switching cycle-with-intermediary services to cycle-with-rc
  if they did not do any intermediary release by milestone-2 [2]

We failed to update process accordingly. These changes add a couple
of steps in the release process, and makes a few other irrelevant.

[0] http://lists.openstack.org/pipermail/openstack-dev/2018-September/135088.html
[1] http://lists.openstack.org/pipermail/openstack-dev/2018-October/135689.html
[2] http://lists.openstack.org/pipermail/openstack-discuss/2018-December/000465.html

Change-Id: Id53275e73bc19418307d7197d7c2f29c09b0233c
2019-02-08 15:44:54 +01:00
Thierry Carrez
50258742c9 Add script to facilitate MembershipFreeze handling
This script will compute a list of deliverables present in
governance but unknown to release management, for manual
processing.

Change-Id: Ibebf777911416d978ecea5ba8d7b25b211e7ae52
2019-01-16 22:34:21 +01:00
Sean McGinnis
6369060496
Update docs with cycle-with-rc information
Adds descriptions and references to the cycle-with-rc model.

Change-Id: I734a9344ce6b2456611708e59bbdd32c0403400e
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
2018-10-24 08:42:36 -05:00
Sean McGinnis
8155e84046
Update cycle-trailing process
Update process document to reflect changes in the cycle-trailing
deadline.

Change-Id: I428991368f02f2aeaa5dfb8303bbe4b040ba97b7
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
2018-09-04 12:09:38 -05:00
Sean McGinnis
727d9c37df
Adjust missed branching process
Sometimes creating the branches immediately for projects can comes as a
surprise and cause a little extra work with backports when they have
critical fixes to include with a requirements FFE. To avoid some of
this, change the branch creation policy to allow it at freeze time but
do not enforce it as a requirement. Then create the branches for any
missed deliverables closer to the end of the cycle.

Change-Id: Ib6f4037c450a00080a5e9a2a7665c6ea4d112ba5
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
2018-08-03 10:59:21 -05:00
Doug Hellmann
96cd9848f0 document another reason to force tags on intermediary projects
Change-Id: I14d9d32b5191a4f90dfe357143d5a2214d13b36b
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
2018-07-20 11:34:47 -04:00