EOL Neutron and neutron-lib stable/train release
As discussed in the ML [1], this patch is closing the missing projects in the stable/train release. [1]https://lists.openstack.org/pipermail/openstack-discuss/2023-September/035000.html Change-Id: Ic4fd21fed278a96951e0a570a7d48eb117b089dc
This commit is contained in:
parent
f0cd7bd43b
commit
0916822310
@ -35,6 +35,10 @@ releases:
|
||||
projects:
|
||||
- repo: openstack/neutron-lib
|
||||
hash: d53744e0370096048aea8f394fa1a7342c774fd6
|
||||
- version: train-eol
|
||||
projects:
|
||||
- repo: openstack/neutron-lib
|
||||
hash: dcb866032452b90270d620951a17d3a8de9433d6
|
||||
branches:
|
||||
- name: stable/train
|
||||
location: 1.29.1
|
||||
|
@ -63,6 +63,10 @@ releases:
|
||||
projects:
|
||||
- repo: openstack/neutron
|
||||
hash: 0f18d406a4134cf769fdf6f2a004c98cbe409215
|
||||
- version: train-eol
|
||||
projects:
|
||||
- repo: openstack/neutron
|
||||
hash: 63bac0fb435d66ab3d1e1775435a5b6ab6752c6e
|
||||
cycle-highlights:
|
||||
- When different subnet pools participate in the same address scope,
|
||||
the constraints disallowing subnets to be allocated from different
|
||||
|
Loading…
Reference in New Issue
Block a user