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: I69dd45f35115a191aa64c8b04c67bc0cedc7dc52
This change updates the release model of Puppet OpenStack based on
the discussion during the previous release[1]. For these repos we do
not create rc but directly release GA.
[1] https://review.opendev.org/c/openstack/releases/+/860887
Change-Id: I7cb24dcdfa53789dbeec482c33cd9975e094bc54
This creates release for Puppet OpenStack modules which support
Zed release of OpenStack components.
Following the existing tags, we do not create the rc1 tag but directly
releases the GA version. In case any critical problem is found after
this release, we create a release with a bumped version.
Change-Id: I074f4605c465ea38486ca509e0b4c4891fafabad
In the past, Puppet OpenStack project created a release per milestone.
However this is not really beneficial because modules should be used
with the actual release of services, while it causes additional
maintenance costs.
We discussed this in ml[1], and agreed to move to cycle-with-rc release
model so that we create only a single release per cycle.
[1] http://lists.openstack.org/pipermail/openstack-discuss/2022-January/026872.html
Change-Id: Idb7a953c4dcd18bf59f2ae7b100acfaf6332eaf7
