list_eom_stale_branches.sh does not work for antelope, where the branch
name has the new style (stable/2023.1) as it tries to search for
stable/antelope, which is wrong. This patch fixes this issue to use
the new stable/<release-id> style.
Change-Id: I6bac959e6346f333c07c31d15c19e6ed54e324b5
This is a library release for python-ironicclient for the Epoxy-1 milestone.
This repository contains commits that have not been released for this
cycle yet.
If the team is ready to process with this release, please leave a +1
to indicate we should go ahead with the release.
If the team needs more time for things about to merge, or if there is
some other reason a release should not be done at this time, please
leave a -1 with a comment indicating the status. Then update the patch
with the new commit hash to use once the team is ready to do the
release.
Change-Id: I23533804481aab77afb91e177b9e23b51f0295ef
Signed-off-by: Elod Illes <elod.illes@est.tech>
Doing this in preparation of the final
antelope release with a missing bugfix
from releases on this stable branch
% git log --oneline --no-merges 17.3.0..
3542e4852 NetApp: don't check kerberos config on mgmt LIF.
Change-Id: I4e161972175775437c3beb8f987347ac5d61bfb9
Doing this in preparation of the final
antelope release with a missing bugfix
from releases on this stable branch
% git log --oneline --no-merges 18.2.0..
a1030e8e5 NetApp: don't check kerberos config on mgmt LIF.
Change-Id: Ic4abab892f6c1e121144c6e506c52c9db4ffc112
This branch reached the end of its official stable maintained period,
hence this patch transition stable/2023.1 branch to Unmaintained. (For
details about Unmaintained state please see: [1][2])
The transitions is as follows:
- tip of the stable/2023.1 branch is tagged with 2023.1-eom tag
- unmaintained/2023.1 branch will be cut from 2023.1-eom tag
- stable/2023.1 branch will be deleted
Note:
- there will no longer be official releases off of 2023.1 branch after
this transition
- backports can be pushed to unmaintained/2023.1 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 2023.1 Antelope stable release
with backports currently in flight that we should wait for. For the
latter case, please propose a final 2023.1 Antelope stable release
patch, and rebase this patch on top of that, with the latest commit
hash of stable/2023.1.
The planned transition deadline was October 30th, 2024 [3] last week,
so please approve this patch as soon as possible if the project is
ready for the transition.
[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: I214e8b1fc6838b6dd3bf64332166ac7815b8a655
This branch reached the end of its official stable maintained period,
hence this patch transition stable/2023.1 branch to Unmaintained. (For
details about Unmaintained state please see: [1][2])
The transitions is as follows:
- tip of the stable/2023.1 branch is tagged with 2023.1-eom tag
- unmaintained/2023.1 branch will be cut from 2023.1-eom tag
- stable/2023.1 branch will be deleted
Note:
- there will no longer be official releases off of 2023.1 branch after
this transition
- backports can be pushed to unmaintained/2023.1 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 2023.1 Antelope stable release
with backports currently in flight that we should wait for. For the
latter case, please propose a final 2023.1 Antelope stable release
patch, and rebase this patch on top of that, with the latest commit
hash of stable/2023.1.
The planned transition deadline was October 30th, 2024 [3] last week,
so please approve this patch as soon as possible if the project is
ready for the transition.
[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: Ie96c4177ef87d93dc52ddf2ef24dc43ff85b4a9b
This branch reached the end of its official stable maintained period,
hence this patch transition stable/2023.1 branch to Unmaintained. (For
details about Unmaintained state please see: [1][2])
The transitions is as follows:
- tip of the stable/2023.1 branch is tagged with 2023.1-eom tag
- unmaintained/2023.1 branch will be cut from 2023.1-eom tag
- stable/2023.1 branch will be deleted
Note:
- there will no longer be official releases off of 2023.1 branch after
this transition
- backports can be pushed to unmaintained/2023.1 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 2023.1 Antelope stable release
with backports currently in flight that we should wait for. For the
latter case, please propose a final 2023.1 Antelope stable release
patch, and rebase this patch on top of that, with the latest commit
hash of stable/2023.1.
The planned transition deadline was October 30th, 2024 [3] last week,
so please approve this patch as soon as possible if the project is
ready for the transition.
[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: Ieb846d87d9dc8acc3164bdb144f287dca2f6679a
This branch reached the end of its official stable maintained period,
hence this patch transition stable/2023.1 branch to Unmaintained. (For
details about Unmaintained state please see: [1][2])
The transitions is as follows:
- tip of the stable/2023.1 branch is tagged with 2023.1-eom tag
- unmaintained/2023.1 branch will be cut from 2023.1-eom tag
- stable/2023.1 branch will be deleted
Note:
- there will no longer be official releases off of 2023.1 branch after
this transition
- backports can be pushed to unmaintained/2023.1 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 2023.1 Antelope stable release
with backports currently in flight that we should wait for. For the
latter case, please propose a final 2023.1 Antelope stable release
patch, and rebase this patch on top of that, with the latest commit
hash of stable/2023.1.
The planned transition deadline was October 30th, 2024 [3] last week,
so please approve this patch as soon as possible if the project is
ready for the transition.
[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: I7f97a91fa092d0179cd2200d352f92515b0d0169
This branch reached the end of its official stable maintained period,
hence this patch transition stable/2023.1 branch to Unmaintained. (For
details about Unmaintained state please see: [1][2])
The transitions is as follows:
- tip of the stable/2023.1 branch is tagged with 2023.1-eom tag
- unmaintained/2023.1 branch will be cut from 2023.1-eom tag
- stable/2023.1 branch will be deleted
Note:
- there will no longer be official releases off of 2023.1 branch after
this transition
- backports can be pushed to unmaintained/2023.1 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 2023.1 Antelope stable release
with backports currently in flight that we should wait for. For the
latter case, please propose a final 2023.1 Antelope stable release
patch, and rebase this patch on top of that, with the latest commit
hash of stable/2023.1.
The planned transition deadline was October 30th, 2024 [3] last week,
so please approve this patch as soon as possible if the project is
ready for the transition.
[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: Icbf65ade54c401051023c05d8df0ecde6256c79d
This branch reached the end of its official stable maintained period,
hence this patch transition stable/2023.1 branch to Unmaintained. (For
details about Unmaintained state please see: [1][2])
The transitions is as follows:
- tip of the stable/2023.1 branch is tagged with 2023.1-eom tag
- unmaintained/2023.1 branch will be cut from 2023.1-eom tag
- stable/2023.1 branch will be deleted
Note:
- there will no longer be official releases off of 2023.1 branch after
this transition
- backports can be pushed to unmaintained/2023.1 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 2023.1 Antelope stable release
with backports currently in flight that we should wait for. For the
latter case, please propose a final 2023.1 Antelope stable release
patch, and rebase this patch on top of that, with the latest commit
hash of stable/2023.1.
The planned transition deadline was October 30th, 2024 [3] last week,
so please approve this patch as soon as possible if the project is
ready for the transition.
[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: I2e27c3d0dd39c41223671630fdccd83187c4ea5e
This branch reached the end of its official stable maintained period,
hence this patch transition stable/2023.1 branch to Unmaintained. (For
details about Unmaintained state please see: [1][2])
The transitions is as follows:
- tip of the stable/2023.1 branch is tagged with 2023.1-eom tag
- unmaintained/2023.1 branch will be cut from 2023.1-eom tag
- stable/2023.1 branch will be deleted
Note:
- there will no longer be official releases off of 2023.1 branch after
this transition
- backports can be pushed to unmaintained/2023.1 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 2023.1 Antelope stable release
with backports currently in flight that we should wait for. For the
latter case, please propose a final 2023.1 Antelope stable release
patch, and rebase this patch on top of that, with the latest commit
hash of stable/2023.1.
The planned transition deadline was October 30th, 2024 [3] last week,
so please approve this patch as soon as possible if the project is
ready for the transition.
[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: I87b0880e3e607d633eba2218be950ef2c38f79e4
This branch reached the end of its official stable maintained period,
hence this patch transition stable/2023.1 branch to Unmaintained. (For
details about Unmaintained state please see: [1][2])
The transitions is as follows:
- tip of the stable/2023.1 branch is tagged with 2023.1-eom tag
- unmaintained/2023.1 branch will be cut from 2023.1-eom tag
- stable/2023.1 branch will be deleted
Note:
- there will no longer be official releases off of 2023.1 branch after
this transition
- backports can be pushed to unmaintained/2023.1 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 2023.1 Antelope stable release
with backports currently in flight that we should wait for. For the
latter case, please propose a final 2023.1 Antelope stable release
patch, and rebase this patch on top of that, with the latest commit
hash of stable/2023.1.
The planned transition deadline was October 30th, 2024 [3] last week,
so please approve this patch as soon as possible if the project is
ready for the transition.
[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: If1fc36d75758a657dfbaa64f19f9fcec99b03a2a
This branch reached the end of its official stable maintained period,
hence this patch transition stable/2023.1 branch to Unmaintained. (For
details about Unmaintained state please see: [1][2])
The transitions is as follows:
- tip of the stable/2023.1 branch is tagged with 2023.1-eom tag
- unmaintained/2023.1 branch will be cut from 2023.1-eom tag
- stable/2023.1 branch will be deleted
Note:
- there will no longer be official releases off of 2023.1 branch after
this transition
- backports can be pushed to unmaintained/2023.1 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 2023.1 Antelope stable release
with backports currently in flight that we should wait for. For the
latter case, please propose a final 2023.1 Antelope stable release
patch, and rebase this patch on top of that, with the latest commit
hash of stable/2023.1.
The planned transition deadline was October 30th, 2024 [3] last week,
so please approve this patch as soon as possible if the project is
ready for the transition.
[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: Id154c21b9ae090414f65ea2d65d734e4b7e93325
This branch reached the end of its official stable maintained period,
hence this patch transition stable/2023.1 branch to Unmaintained. (For
details about Unmaintained state please see: [1][2])
The transitions is as follows:
- tip of the stable/2023.1 branch is tagged with 2023.1-eom tag
- unmaintained/2023.1 branch will be cut from 2023.1-eom tag
- stable/2023.1 branch will be deleted
Note:
- there will no longer be official releases off of 2023.1 branch after
this transition
- backports can be pushed to unmaintained/2023.1 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 2023.1 Antelope stable release
with backports currently in flight that we should wait for. For the
latter case, please propose a final 2023.1 Antelope stable release
patch, and rebase this patch on top of that, with the latest commit
hash of stable/2023.1.
The planned transition deadline was October 30th, 2024 [3] last week,
so please approve this patch as soon as possible if the project is
ready for the transition.
[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: I7000a591cae089df7ac512eb92ff56af0fc26b69
Validator originally checked for <series>-{eol,eom,em,last} tags.
Since we are using branch IDs since Antelope, the validator has to
accept for example 2023.1-eom, 2023.1-eol and 2023.1-last tags instead
of antelope-<..> tags.
Change-Id: I584c34a533db25a29206606d81d95ad2daa7779c
Explicitly add setuptools as a dependency so that the call to
wheel.bdist_wheel in openstack_releases/links.py does not fail.
Change-Id: I66378e04db045e97f4d907eff0369738006291b1
cinder: 23.3.0 (minor bump to accommodate ec37accf6)
os-brick: 6.4.2
not being released at this time:
cinderlib: no functional changes
python-brick-cinderclient-ext: no functional changes
python-cinderclient: no functional changes
Change-Id: Ic4a9a89e9a11b71c26408bdb210656b5c6e227d8
cinder: 24.2.0 (minor bump to accommodate 2bb2f13de)
os-brick: 6.7.1
not being released at this time:
python-brick-cinderclient-ext: no functional changes
python-cinderclient: no functional changes
Change-Id: Ia0114f961d4927d279fd77bb5250b06f55438816
This release mainly includes the default value of
policy_file to policy.yaml and releasing it early
in this cycle help to consume the same in upstream
testing.
Change-Id: I2a044eaa79b2590c408ab13610b9b9e5df16127a
... to make a few bug fixes available in a released version. Especially
the fix to reduce noisy log message[1] is useful in large deployments.
[1] 8ab852f334c46297870486af18c9cac0272f09fa
Change-Id: I8be3180222809fa441afa6430f39d0674146c42d