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
This new section in our Cycle Information email template emphasizes
how important it is to get PTL and release liaison reviews as soon as
possible, in order to keep the schedule and its deadlines.
Change-Id: I8706b6fff5a72cf776d06b5205399b5d118a37d4
The process autorelease command for milestone-1 was missing a backward
slash in the command in (2) after the --type library
Now, the command has the right forward slash that looks like this:
--type library \
Change-Id: I852497033ff15d85fda50c61f4ec60bd2e4cc881
Signed-off-by: Armstrong Foundjem <foundjem@ieee.org>
This adds a listing for the 2023.2/Bobcat Cycle key fingerprint with
Friday 2023-03-31 (the week after the 2023.1/Antelope release) as
its start date, and links to an export of the corresponding public
key with initial attestation signature from the 2023.1/Antelope
Cycle key as well as the change author.
Change-Id: I9aaf9b7d513f6b2845a518c84ea2c381ff297220
The new release identification / naming schema [1] (like:
2023.1 Antelope) broke the redirection rules for branch specific upper
constraint files as the stable branch names are from now on based on
the new release identification (like: stable/2023.1).
This patch fixes the redirections by introducing the release ID field
to series status, to translate a release name to 'stable/<release-id>'
where this ID exists.
[1] https://governance.openstack.org/tc/reference/release-naming.html
Change-Id: Iab885d4e36f64903b323e16c74d8315c759584de
This is a proposed release schedule for OpenStack 2023.2 "Bobcat",
with a total duration of 28 weeks.
Change-Id: I74f77cadd76ea887d8aa5b79251615c78d46aa1a
This patch adds to the Releases page template the possibility to
indicate whether a release is a SLURP release.
Change-Id: Ie0dcddfe271e8fd77a6d40fa54c8ef2ee6914b78
Most of the deadlines (milestones) should be on Thursdays (except the
final release, which is on Wednesday traditionally).
Change-Id: I3cd54fec5abe7ae18796f575241137d8728517ca
This sets the end date for the Zed key, and sets the start for the
2023.1/Antelope key coincident with the merger of the corresponding
I141514eaf31b2249f0901ad1ff93cc1bbe940c2d change.
Change-Id: I65a360d61d28ce4980a6ef7540157e4f67869c72
Sphinx4 produces a different structure, so the CSS hack that was posted
to avoid duplication of titles no longer works. Apply the same hack to
the new structure.
See also: https://review.opendev.org/798897
Change-Id: Ic7eb8b90e5d68f390ef9015fa41dddac943cba3a
