Dalmatian release schedule had a few off dates for milestones in the
schedule details section. Also use US English format for dates, as the
project standardizes on US English for communications.
Change-Id: I59876e34091a651ec322635eb90578f457e8bd92
We no longer have branches in extended maintenance state, these have
been switched to Unmaintained (eom). So we need to check for the latter
state when listing branches that could be deleted since the are EOLed.
Add oslo.utils to requirements since it is now needed by the
tools/delete_stable_branch.py script.
Change-Id: Ib948befa6f2706dc5dc50009b021af3a1bb389a8
This adds a listing for the 2024.2/Dalmatian Cycle key fingerprint
with Monday 2024-04-08 (the week after the 2024.1/Caracal release)
as its start date, and links to an export of the corresponding
public key with initial attestation signature from the
2024.1/Caracal Cycle key as well as the change author.
Change-Id: Ie9d1ab692893fdec2dfb99abf1e88efcfb31f693
Teams tend to forget about clean up their unnecessary jobs or unused
special nodesets, etc. This patch adds a notification for the teams
to the process guide at week R-3.
Change-Id: I5f6a236b93ae0f4ed5b913aca8e3ebf6c2196f7f
When trying to add this I noticed that there are duplicate
'project-specific' in the schedule for R-7, merge into a single list.
Depends-On: https://review.opendev.org/c/openstack/election/+/905152
Change-Id: I5e4be324118c7c47118ba39a5d29c7046755c9ca
To delete stable/<series> branches first we have to abandon all open
changes otherwise gerrit does not allow to delete the branch.
This script abandons all the open patches on a given project on a
specific branch.
Change-Id: I431fb305f998608889510f8ed2914583891d2167
Fix language used to drag attention to cycle highlights in R-5 release
status email as the deadline shifted.
Change-Id: Ie47ace9bb7c7473e977178ffce0b64cd8ee4b9c0
This is based on the list_eol_stale_branches.sh script to make it
possible to delete stable/<series> branches where there are
<series>-eom tag already.
Change-Id: Iaaa9702c5b304152492ed2afc56ac07fb9c9fb98
Update R-8 email template in PROCESS document to match the one that was
sent for 2024.1 Caracal cycle.
Change-Id: I453ffa9e7b022a01c178d082d551543ab6ce16cc
- Train and Ussuri will transition to End of Life
- The last 3 series in Extended Maintenance will transition to
Unmaintained (Xena, Wallaby, Victoria)
- Yoga is now Unmaintained
- Zed and newer branches will transition to Unmaintained after their
3rd subsequent series is officially released (~18 months)
This patch also:
- extends the note about the maintenance phases
- refines Zed's planned transition date to Unmaintained to a less busy
date, ~1 month after the official 2024.1 Caracal release
Change-Id: I860f5056a5563c1e8377dfc7d4f9c31f28912e3c
This is a proposed release schedule for OpenStack 2024.2 Dalmatian.
26 weeks long cycle, with 2 October, 2024 as planned release date.
Change-Id: I8bf5d0ade01a81b1cfd340dce42e31d74a999a96
We agreed with PTLs and Foundation some cycles ago that the cycle
highlights deadline can be at week R-4, just after Feature Freeze.
Otherwise Feature Freeze week would be too busy for PTLs (it's
busy enough with dealing the FF itself).
Change-Id: I5f10342120d01781c29ee72856f36a15f3d4fcae
It has been agreed to use term Active Contributors rather then
Active Technical Contributors across the board to highlight importance
of non-technical contributions.
Depends-On: https://review.opendev.org/c/openstack/governance/+/893831
Change-Id: I067e703ef52a16e18bc6de76f7c8842a2726cb42
Series goals are now longer applicable however, goals
still exists so replace the corresponding section in our M1
email template.
Change-Id: I754af9aa7a4cc02f46592628e1c0a18170ea55df
Previous patch [1] that normalized the cycle key letters to be
lower-case accidentally removed the .txt extension. This patch
adds it back again.
[1] Ib08e17b79d3fe20e7dc2c0c43305ff77ee3a6530
Change-Id: I05c732baa751ec4373e29e532c1d2ec2bba45280
This adds a listing for the 2024.1/Caracal Cycle key fingerprint
with Monday 2023-10-09 (the week after the 2023.2/Bobcat release) as
its start date, and links to an export of the corresponding public
key with initial attestation signature from the 2023.2/Bobcat Cycle
key as well as the change author.
Change-Id: Ia80b2e739959b96fe26214868178727bf1883988
When the 2023.2/Bobcat Cycle signing key was added, an upper-case
representation of its fingerprint was used. Prior cycles listed
theirs in lower-case, so fix this for consistency before we document
any new keys.
Change-Id: Ib08e17b79d3fe20e7dc2c0c43305ff77ee3a6530
A few instances of '2023' should be '2024'. (The day of the month
looks correct, it's just the year that wasn't updated.)
Change-Id: I17c0ab67c664f7f2b30cf724d75c3b6952c30296
Here is the proposed release schedule for OpenStack 2024.1 "Caracal".
This is a 26-week cycle with a final release date on April 3, 2024.
It has a longer milestone-2 period to accomodate Thanksgiving and
end-of-year holidays.
Also fix an issue in Bobcat release schedule where Antelope cycle-trailing
deliverables were mentioned as Bobcat cycle-trailing deliverables.
Change-Id: I0fb0e61e79e7e4c51d42cabd7c05bb15a05275fa
Currently we're reverse sorting with a simple sort, this sadly puts
newer released (antalope, bobcat) at the end of the list. Add a
key function that has context around our release names and release ids
to sort "2024.1/cantaloupe"[1] at the top.
[1] As of now the c name isn't selected cantaloupe is my placeholder
Change-Id: I4b021d99bd4ecc232838a3639dd8d5ef075e1a24
Thierry Carrez