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
This sets the end date for the Yoga key, and sets the start for the
Zed key as today,coincident with the merger of the corresponding
I86e393994c80b0d73df21e62182a75e4b047b1c7 change.
Change-Id: I4d3859a6e0223fa6c805ac22c814434f8e51db7f
A routine 404 check revealed that some links in our footer were leading
to 404 pages. This updates the footer on releases.o.o so that it is
consistent with the one displayed on openstack.org main website.
Change-Id: Icc9290fb07ea4083b1499f1a245bad2e686759c8
The TC tags framework is discontinued [1], so all references to TC tags
will be invalidated once TC passes the change.
This patch removes the use of '--tag stable:follows-policy' from helper
scripts.
[1] http://lists.openstack.org/pipermail/openstack-discuss/2022-February/027214.html
Change-Id: I30645f45c270f436605ef5024557e341a6851dce
The current date settings for the Yoga R-13 week goes until 31 December,
2022, resulting in this week lasting for over a year. This shows up on
the calendar for anyone subscribed to either the Yoga ICS calendar or
the overall combined calendar.
This corrects the end date to Friday the 31 December, 2021 when that
week ended.
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
Change-Id: I28b43577e94b887e133f1cb954b7eb601788940e
This adds a listing for the Zed Cycle key fingerprint without a
start date yet, and links to an export of the corresponding public
key with initial attestation signature from the Yoga Cycle key as
well as the change author.
Change-Id: I15ced779782163fc9e85b5ba10481a076aafdf2c
All strings are considered as unicode string from Python 3.
This patch drops the explicit unicode literal (u'...')
appearances from the unicode strings.
Change-Id: I40185b08a9e415f416c45608cf90c8f515755222
I have verified the correctness of the key according to the copy
stored on bridge.
Also update the recommended signature listing command line to
include some specific output options which will hopefully make the
comment block somewhat more stable and reviewable.
Change-Id: I8aae021fc9ffba3ed1e52cf319b7df44545fbf53
This sets the end date for the Xena key, adds the Yoga key starting
today and links to an export of the corresponding public key. It
also drops references to the now defunct SKS keyserver network and
our old rotation process which was tied to it. Instead the key has
been created following the new process described by change
I7008706aae06b6e4a16db2dd85a8c7f91530cd50.
Depends-On: https://review.opendev.org/815548
Change-Id: I53f11a249b5e09c84d65644ee609553a9b6e6353
The release team involvement ladder and infrastructure primer were
hard to find in CONTRIBUTING.rst. It's better to move them next to
the rest of the team documentation.
Change-Id: I3859ce431711cef5176a3ea34b9433bd06d51447
This sets the end date for the Wallaby key, adds the Xena key
starting today and links to a minimal export of the corresponding
public key and its details on the keyserver network.
Change-Id: I012696f62c41915b71dfc12f3c658decc26e9644
Branching the devstack-plugin-* is missing since 2 cycles
(victoria/wallaby), these changes add a related task at R-3 to
ensure to not miss them anymore.
Some tasks of R-2 aren't crystal clear about the expected state of the
series branching.
Some commands are more or less duplicated and inefficient.
Indeed, the QA PTL should be "reminded" once branching is done but the
checks are made after. Also we previous version of this doc was using
two commands who are more or less similar, however, one of them doesn't
caught the `cycle-with-intermediary` deliverables and also doesn't ignore
trailing projects (branching isn't mandatory at this point for them).
These changes remove the duplicated commands and prefer to use the
better one.
These changes reorder steps to "remind" people at the right time and when
all prerequisite are there.
Change-Id: I765e74b15e1f8fc6e45fb90662d04464faf17640
Previously the tempest plugins were driven by the legacy
`cycle-automatic` model. However this model have been abandoned.
The cycle-automatic release model is now better described by the
`cycle-with-intermediary` model combined with `stable-branch-type: none`
The `cycle-automatic` model was used by specific technical deliverables
that needed to be automatically released once at the end of a cycle.
the tempest-plugin are branchless and `cycle-with-intermediary`
however our process doesn't handle them at the end of the cycle
like did the `cycle-automatic`.
These changes clarifying that point.
Change-Id: I6b3619a44d0aea1fa4852e650cbafcb08c853353
