Now that ussuri-2 is past us, update the process to add
weekly email content that was posted during those weeks.
Change-Id: I738a1678e7a236ce8fb30de25978bac6a2db680a
In releases.o.o we display signature links for all deliverables,
if the series is > Ocata or independent. Since some "independent"
deliverables predate the signature generation tooling, that results
in a number of "independent" deliverables displaying broken signature
links, which makes us look bad.
This adds a flag (skipped-sig) that can be set for independent
deliverables that did not have any signature generated (pre-Ocata), and
skips the signature link display if the flag is set.
As a practical example, this fixes broken links for PBR<2. Tony signed
up to automatically generate the others.
Change-Id: I44a49e3f08010a85c64673d2292528139eabcc99
get-contacts:
To extract the PTL/Liaison contact information from the governance data
/ release team data
tools/bulk_review.sh:
To manipulate a dirty working-tree and post as a single gerrit topic,
one change per team. Changes are unordered so any change can be merged
when it's ready/ approved by the appropriate team
Also enhance get-deliverable-owner: to detect file paths
Story: 2005704
Task: 31028
Change-Id: Ia319e8a7b4da195cb4bc861c51025a41adc43bb3
This updates our sphinx extension to show abandoned deliverables
as EOL, in a separate section at the bottom of the independent
deliverables page. It adds an 'EOL' mention to such deliverables
on team pages.
Change-Id: I56b9fbad9314c523e2f18765371746d21a71ed88
We have been filtering whether to include pgp links for deliverables if
the series was >= 'O', which resulted in filtering out any independent
deliverables.
This updates the check to account for independent deliverables. It also
makes the table format consistent for pre- and post-Ocata, just leaving
the column blank for series where we did not generate signatures.
Change-Id: I0c9f97cb12a429d2e54d94df2b3e110156278bc1
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
Our docs job has a lot of output that is not generally very useful.
Rather than bloating our log files, this switches some log calls over to
debug level so they are only emitted if needed.
Change-Id: Id0440ef506d0bc896d6dd4ba30473f430a6606dd
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
Introduce an 'abandoned' release model for cycle-independent
deliverables. It should only be applied to deliverables in the
_independent directory. No new release should be accepted for
deliverables with this release-model.
Change-Id: I65c163888c37f7a7f77273abf3ca0633923a0fe2
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
The propose-update-constraints job was referred to as
propose-upper-constraints. Update name to make it a little easier if
someone is looking for references to the actual job.
Change-Id: I707b2a498af491c9d2e481ed1880ad74839c9389
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
The deadline for projects following the cycle-trailing release
model is 3 months after the coordinated release. Add a note
to the Ussuri schedule at R-18 (12 weeks after the Train release).
Change-Id: If1ac66fd6b0e52d86d762bf05674e310bd3d7934
This is the first step into automating PTL/liaison approval.
This tool will check that PTL/liaisons either authored the change or
approved it.
Change-Id: I1bbb371997e9e92f39eff47adb4d3d176af35de7
We want these tags in git for developers and those working directly with
the source code, but we do not want to have these listed on the releases
site. Consumers of the site are just looking for actual official
releases they can use, so we should avoid confusion by not including
these "internal" tags.
Change-Id: I6a3fcc11efed6254ea6fb95579eafe5288508661
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
Having "estimated TBD" looks silly in the table, replace this by just
"TBD" if we don't have a date set yet.
Change-Id: I48394304b48e7ec36e51a2b8b036ee5e60cb016d
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
Manila feature freeze was called out for the same time as the overall
feature freeze. This removes it since there is no additional information
or different date for the project specific deadline.
Change-Id: I253f316a64b40048d74b93a06e238a69b0bda242
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
This sets the end date for the Train key, adds the Ussuri key
starting today and links to a minimal export of the corresponding
public key and its details on the keyserver network. This can be
amended with a new patchset or a follow-up change to correct the
included dates after the key material change (Depends-On below)
merges and goes into effect.
Depends-On: https://review.opendev.org/691939
Change-Id: Id8e4d24fa18cccffb2da3acd987cfbf01efd3bae
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>
This patch aims to make possible to provide SHA commit
for https://releases.openstack.org/constraints/upper/ URL
in addition to branch or tag. This is heavily used by OSA to be sure
that every time role is runned under some release it will install
the same package versions.
And to be consistent and use releases.openstack.org for contraints
not only in tox but in role itself this patch is needed.
Change-Id: I1ce0af2ab2163ea1f154516229889b3cf8813ab6
Oslo freezes one week before non-client library freeze. We need to
note that in the release schedule.
Change-Id: I83713017b29ae900ccc9f3263e483984c3abc440
Some are linking directly to the highlights pages for release cycles as
a sort of top level release note page. This content is very raw and the
quality of the items listed really varied team by team.
This adds a note at the top of the pages to make sure it is clear to
anyone reading it that the content on the page is not something that can
be taken directly as the marketing information for a release.
Change-Id: I9bc3a94e0cd63735b0234f3cfb10817ee3b84c66
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>