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
Client libraries (and other libraries strongly tied to another
deliverable) should generally follow their parent deliverable release
model, even if they did not have a lot of activity themselves.
Rephrase 'evaluate' task to only consider non-client libraries for
model change.
Change-Id: Ifbe2889ada78cf52c56e6d261f47883300033f4d
R-3 week's task for unreleased cycle-with-intermediary deliverables
contains also '--type tempest-plugin' however there is a dedicated task
for them in R-2. This patch keeps the dedicated task and removes the
redundant one from R-3.
This patch also adds a note with some task details to the modified task
to make it more clear.
Change-Id: I41906a133ff8925a5ed08b4bc52229e279651acb
This adds a listing for the 2023.1/Antelope Cycle key fingerprint
without a start date yet, and links to an export of the
corresponding public key with initial attestation signature from the
Zed Cycle key as well as the change author.
Change-Id: I2a99cc820aa84ada9de4813db53b9413cf223c2d
Cycle Highligts original deadline was the same as Feature Freeze date.
This caused extra burden to PTLs as while they were reviewing the last
patches at FF, they also needed to write the highligts at the same
time.
This patch postpones one week the Cycle Highlights task so that the
deadline indicates more that is needed AFTER the projects feature
freeze, but still gives the time to Marketing team to process the
cycle highligts.
Note that the best is to collect the Cycle Highlights in advance as
much and as soon as possible, because for Marketing team perspective
having an incomplete list of highlights is better than waiting until a
complete list can be constructed.
Change-Id: Ibe8f0faebcce480bac79a789fb689112038b48c8
From some point gerrit started to allow maximum 9 sections in its
dashboard, and the ~1 month period (after the latest release AND before
the oldest maintained series to transition to 'extended maintained')
the dashboard fails as we have 10 sections then.
With patch I9226e7b7e9b9594daa11d97bd6a8b4b04c56f596 the 'All Releases'
section was deleted to make the dashboard working again all the time.
Unfortunately, that resulted we don't see every patch on our dashboard
so this patch adds back the 'All Releases' section. To not to break the
dashboard, Jobs and Tools sections are united. With this we will have
9 sections in the ~1 month period and 8 sections for the rest of the
time of the cycles.
Furthermore, 'Other' section is extended to list EOL patches to
highlight them as well. (EOL patches would be better to have a separate
section, but with that we would exceed the maximum allowed sections
number in the above mentioned ~1 month period)
Change-Id: Ia9abb0ac39b39f1dd8408aa3d576137f7b95af8b
As some deliverables don't really fit the cycle-with-rc model but
released only once per cycle, the process would still suggest the model
change. This patch adds a note that for such cases the model change
is not a must.
Change-Id: I3ae583dab2df800a40fbca449fd2e6f08425bd5a
The releases dashboard link does not work properly recently. It seems
that there are two problem with the link:
* the link does not need the '#' anymore
* due to some reason the 'All Releases' query messes up the dashboard
(at first place it does not need the 'is:open' part because it's
added already with 'foreach', secondly it gives an error message:
'Error 400 (Bad Request): limit of 10 queries'). Nevertheless, 'All
Releases' is probably not that important as all the release patches
are covered with series sections together with 'Others' section
(except deliverables under 'deliverables/<series_in_EM_or_EOL>/*').
So this patch fixes the dashboard by removing 'All Releases' section.
Note: This problem comes even under Firefox or Chrome (when signed in).
Change-Id: I9226e7b7e9b9594daa11d97bd6a8b4b04c56f596
