This patch adds OpenStackSDK project specific feature freeze for
python-openstackclient to 2025.1 Epoxy and 2025.2 Flamingo cycles.
Change-Id: I9c797b7c103b6e120219f942c1696613721d17e3
As agreed on PTG, to avoid late discoveries that projects are still
using old releases instead of the freshly released ones, this patch
adds a check task after every milestone to ensure that all new
releases are added to upper-constraints.txt.
Change-Id: I9dac536d6d5afc47a971a99bd99b194653f8d0f4
This patch updates the release schedule with the PTG date, as this was
already announced and advertised on openstack.org [1].
[1] https://openinfra.org/ptg/
Change-Id: Ic15168c597f264236d5d5f6c303c227dacb3bf89
When doing the governance consistency check, some false positive may be
detected as the TC maintains a separate list of 'inactive' projects that
should not be released and yet still appear in governance.
Mention the list in the process so that we remember to double-check it.
Change-Id: I591f71b26496b0480d10fad7f165a772b546bedd
The foundation produced a nicer version of the graphviz generated SLURP
diagram that I made and has asked that we include it in the release
docs. This change adds the image and cleans up the graphviz tooling as
it is no longer required.
Change-Id: Iff4ed3d029975f3a4ca3775e0bd3680cd25aec50
Publishing this information on the release
calendar so that we can avoid people missing the
call for nominations that we usually do later
in this Epoxy cycle.
Election dates were proposed in
I92da68161874e7d39b5be4fc97dd6ac93ac82aa8 and
I8fc3b05848e1d2928169d5cb33c5e89349262550
Change-Id: I12e62ebf50461865723ad44f7cda23550ae3edec
This is a proposed release schedule for OpenStack 2025.2 Flamingo.
26 weeks long cycle, with 1 October, 2025 as planned release date.
Change-Id: I9294e1df1915683425b2699dd474ee221f7ee7e5
I think visual representation can help people understand the practical
effects of the SLURP releases on their upgrade options. Lets add one
using graphviz to do the rendering for us.
Change-Id: Ic28c8ad4bc84f094a37b38037a6859d725e85f51
- Clarify that string freezes are applied to I18n target projects
- Fix I18n PTL to I18n SIG per governance change
- Update release liaison for I18n
Change-Id: If256992882a50bebabc3d4873d8512f0f155fc1e
This adds a listing for the 2025.1/Epoxy Cycle key fingerprint with
Monday 2024-10-07 (the week after the 2024.2/Dalmatian release) as
its start date, and links to an export of the corresponding public
key with initial attestation signature from the 2024.2/Dalmatian
Cycle key as well as the change author.
Change-Id: I0ed06b1b114d5a1e0dd80899c2c460d0a7069019
This is a proposed release schedule for OpenStack 2025.1 Epoxy.
26 weeks long cycle, with 2 April, 2025 as planned release date.
Change-Id: I71dc9a7593260180db0a01b722fe38271bbd0acd
It seems that d-mf tag (Membership freeze) was missed from the original
schedule proposal patch, so fixing that by adding it to the usual
Milestone-2 week.
Change-Id: Ic9eed14995ed46233792c2322258732327252a8c
Publishing this information on the release
calendar so that we can avoid people missing the
call for nominations that we usually do later
in this Dalmatian cycle.
Election dates were proposed in
I2cb7351c1f474b092c81f71b5fcff3a2f68c241a
Change-Id: I129d48b549dcf7f1cf55cb4bfed20f99dc362f73
During Caracal release it was discovered late that the openstack map
could use a refresh ahead of release communications. Since we should (in
theory) know the contents of the release (in terms of deliverables)
after milestone-2, add a step in the process to have a look at the map
and submit any necessary changes well ahead of the release week craze.
Change-Id: I51674b19afce0ea7b32f93ee989dbbf9df926f90
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
