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: I567424c888f226e0376ab6700984f5da80c8d648
To include all the changes merged during Caracal cycle.
Support for python versions has been removed so we need to bump major
version.
Change-Id: I5e1f6d98e748ae87d4c165e379f96adff5427902
First Dalmatian release for openstacksdk 3.1.0:
$ git log --oneline --no-merges 3.0.0..HEAD
afdf1549d Add sort_key and sort_dir to core Neutron resources
4b1e75aad Update master for stable/2024.1
c689bbaf6 reno: Update master for unmaintained/xena
aabe1e04b reno: Update master for unmaintained/wallaby
af2c520b9 reno: Update master for unmaintained/victoria
4f46ab3f8 Add support for showing requested az in output
31fe67b83 Fix the mailing list domain in documentation link
d1ff60d12 Fix typo
434adf775 Adding SDK support for ``glance md-namespace-properties-delete``
4faf511f4 identity: Add access rule CRUD support
Change-Id: I6858d504322f8ac800b06f80932c0a62a61a1057
This release contains a lot of relevant fixes for making SQLAlchemy
2.0 work in Manila. With the fixes for SQL Alchemy 2.0, Manila is
now compatible and there should not be any issue when using the
newer version of SQLAlchemy.
List of fixes:
$ git log --oneline 18.0.1..eca9ec1955e929e3da0c14cd0ae4da07eb1166c4 --no-merges
eca9ec195 (origin/stable/2024.1) Fixes for sqlalchemy 2.0
1635d03a1 (gerrit/stable/2024.1) Update TOX_CONSTRAINTS_FILE for stable/2024.1
a941b7499 Update .gitreview for stable/2024.1
Signed-off-by: silvacarloss <ces.eduardo98@gmail.com>
Change-Id: I0ffc68efd3ef13c15e0064918e6033e4105f932d
Create a new taskflow release which contains a fix about SQLAlchemy 2.0
compatibility[1].
[1] d683ddb86eef89074a2ea09a454c8efd8b88561b
Change-Id: I428f8bd643b927d9d5464e331741988244ee91c6
Dalmatian release schedule had a few off dates for milestones in the
schedule details section. Also use US English format for dates, as the
project standardizes on US English for communications.
Change-Id: I59876e34091a651ec322635eb90578f457e8bd92
With the new TC resolution the community replaces Extended Maintenance
with Unmaintained status [1].
So this patch transitions victoria, wallaby, and xena EM branches to
Unmaintained as follows:
- tip of the given branch will be tagged with <series>-eom tag
- unmaintained/<series> branch will be cut from <series>-eom tag
- stable/<series> branch will be deleted
Some further notes:
- stable policy still applies
- backports can be pushed against unmaintained/<series> branch
- openstack-unmaintained-core group have the rights to merge patches
For further details please read the resolution [1] & review and +1 this
patch if this is correct as soon as possible.
[1] https://governance.openstack.org/tc/resolutions/20230724-unmaintained-branches.html
Change-Id: Icdf1ab58449944326e68f2211c6f72c984a2a499
The generated content initializes the 2024.2 Dalmatian cycle's
deliverable files, based on 2024.1 Caracal deliverables.
Change-Id: Id9ed742d46537bd98923ab597cb1b167de488561
With the new TC resolution the community replaces Extended Maintenance
with Unmaintained status [1].
Since Solum project is marked as inactive as there were hardly any
maintenance, we move its old xena, wallaby and victoria branches to EOL
instead of moving them to Unmaintained. If anyone wants to resurrect
the project then the work should be started at the master branch
instead.
[1] https://governance.openstack.org/tc/resolutions/20230724-unmaintained-branches.html
Change-Id: I8806fe0cb5570994e839cadc2cf545e6b59f238a
With the new TC resolution the community replaces Extended Maintenance
with Unmaintained status [1].
Since the senlin project has been marked as inactive by the TC, this
patch transitions victoria, wallaby, and xena EM branches to EOL.
This will also help resolve the zuul config errors that currently
exist for these branches.
[1] https://governance.openstack.org/tc/resolutions/20230724-unmaintained-branches.html
Change-Id: Ia99f9c0d64e2871aac954cf1fa0d6c33d87bc90b
With the new TC resolution the community replaces Extended Maintenance
with Unmaintained status [1].
Since Qinling project is retired after victoria, it makes sense to move
its victoria branches to EOL instead of moving it to Unmaintained.
If anyone wants to resurrect the project then the work should be
started at the master branch instead.
[1] https://governance.openstack.org/tc/resolutions/20230724-unmaintained-branches.html
Change-Id: I92499f8e1a577535266a23b21262a30bcb6f97dd
With the new TC resolution the community replaces Extended Maintenance
with Unmaintained status [1].
Since Karbor project is retired after victoria, it makes sense to move
its victoria branches to EOL instead of moving it to Unmaintained.
If anyone wants to resurrect the project then the work should be
started at the master branch instead.
[1] https://governance.openstack.org/tc/resolutions/20230724-unmaintained-branches.html
Change-Id: I4fee731a235546e36628a084cd5a3d0782752cfc
With the new TC resolution the community replaces Extended Maintenance
with Unmaintained status [1].
Since Murano project is marked as inactive as there were hardly any
maintenance, we move its old xena, wallaby and victoria branches to EOL
instead of moving them to Unmaintained. If anyone wants to resurrect
the project then the work should be started at the master branch
instead.
[1] https://governance.openstack.org/tc/resolutions/20230724-unmaintained-branches.html
Change-Id: I56f00a8b89c6c48620d0f61dc491038d3c10af60
With the new TC resolution the community replaces Extended Maintenance
with Unmaintained status [1].
Since Freezer project is marked as inactive as there were hardly any
maintenance, we move its old xena, wallaby and victoria branches to EOL
instead of moving them to Unmaintained. If anyone wants to resurrect
the project then the work should be started at the master branch
instead.
[1] https://governance.openstack.org/tc/resolutions/20230724-unmaintained-branches.html
Change-Id: I5780c583359eb437eade123075e0dcd05c014b21
With the new TC resolution the community replaces Extended Maintenance
with Unmaintained status [1].
Since Sahara project is marked as inactive as there were hardly any
maintenance, we move its old xena, wallaby and victoria branches to EOL
instead of moving them to Unmaintained. If anyone wants to resurrect
the project then the work should be started at the master branch
instead.
[1] https://governance.openstack.org/tc/resolutions/20230724-unmaintained-branches.html
Change-Id: Idb6c39902653f8d96ea853402eea82db4b7abafd