This branch reached the end of its official stable maintained period,
hence this patch transition stable/zed branch to Unmaintained. (For
details about Unmaintained state please see: [1][2])
The transitions is as follows:
- tip of the stable/zed branch is tagged with zed-eom tag
- unmaintained/zed branch will be cut from zed-eom tag
- stable/zed branch will be deleted
Note:
- there will no longer be official releases off of zed branch after this
transition
- backports can be pushed to unmaintained/yoga branch
- openstack-unmaintained-core (or <project>-unmaintained-core groups if
such exists) have the rights to merge patches
Important: please +1 if the team is ready for us to proceed with this
transition, or -1 if there are any final Zed stable release with
backports currently in flight that we should wait for. For the latter
case, please propose a final Zed stable release patch, and rebase this
patch on top of that, with the latest commit hash of stable/zed.
The transition deadline is May 2nd, 2024. [3]
[1] https://docs.openstack.org/project-team-guide/stable-branches.html#unmaintained
[2] https://governance.openstack.org/tc/resolutions/20230724-unmaintained-branches.html
[3] https://releases.openstack.org
Change-Id: I20e705b79388895b0bcc4b540ff6e8004ea68b0b
This release picks up new commits to keystone since
the last release from stable/zed.
This is being proposed as a convenience to help make sure stable
changes are being released. If the team is good with this going out,
please respond with a +1 to let the release team know it is OK to
proceed.
If it is not wanted at this time, or if there are more changes that
would be good to get merged before doing a stable release, please
leave a -1 with a comment with what the team would prefer. We can
then either abandon this patch, or wait for an update with a new
commit hash to use instead.
$ git log --oneline --no-merges 22.0.1..72a4fc0f3
72a4fc0f3 Add an option to randomize LDAP urls list
Change-Id: I6b6e996d3801073496f276fa044f9dc9389c4768
Signed-off-by: Elod Illes <elod.illes@est.tech>
This tags the final release for all cycle-with-rc projects for Zed.
While not required, having PTLs ack this patch would be nice to include
that record in the merged metadata.
Release activity should now be frozen until this is processed on
October 5th. Any bugfixes merged to stable/zed can be queued up and
ready to go as a follow on stable release after the coordinated release
date.
There are different diff-start values for each project. This is used
when generating release notes to denote the point where the stable/yoga
branch started to diverge from what is included on stable/zed. For
some, this will be the final Yoga major version, but if multiple RCs
were done, this may show the initial RC1 release version. This is
normal.
This patch will be merged on October 5th.
Change-Id: I89c7eb88c86f012536713e1ad7aa5b243aaf7f83
This generated patch adds Zed release note page link if that page
exists for a deliverable.
If any of your deliverables does not have a release note link added
already under deliverables/zed, then please check whether there is an
open patch on that repository with the topic "reno-zed" [1] still
waiting to be approved.
[1] https://review.opendev.org/q/topic:reno-zed
Change-Id: I231327552fb12655a4bd4b5934c3272dfddd6b03
This proposed a RC1 release for keystone to get any merged changes
out prior to the RC1 deadline for Zed going into effect.
If the team is ready to proceed, please leave a +1 to acknowledge this
release and we will process right away. If the team is working on any
final merges, leave a -1 with some detail on the status and update the
patch with the new commit hash to use when ready.
Patches with no response will be merged by early Friday, September 16.
Signed-off-by: Elod Illes <elod.illes@est.tech>
Change-Id: I4e30d400c08b7820e254241f67541d3f75d58104