3b23440f8e
As announced on mailing list [1], this patch transitions the Stein branch to End of Life. The last patch of the branch will be tagged with stein-eol tag. stable/stein branch cannot be used anymore and will be deleted if this patch merges. This is needed as stable/stein is not actively maintained in recent period, thus gates are mostly broken due to job failures. Besides, by removing these branches, infra resources will be freed up, too. Please try to identify any zuul job, that is defined outside of the repositories in this patch (for example in openstack-zuul-jobs, etc.) and won't be used anymore if stable/stein is deleted. Propose a job removal patch for them. Please +1 if the team is ready for us to proceed with this transition, or -1 if there are still some activity on the branch and the team wants to continue to maintain it. [1] https://lists.openstack.org/pipermail/openstack-discuss/2023-September/034965.html Change-Id: I096db543219fe62e2e23ddc5e2280e2279dd206a
47 lines
1.6 KiB
YAML
47 lines
1.6 KiB
YAML
---
|
|
launchpad: congress
|
|
release-model: cycle-with-rc
|
|
team: congress
|
|
type: service
|
|
repository-settings:
|
|
openstack/congress:
|
|
tarball-base: openstack-congress
|
|
releases:
|
|
- projects:
|
|
- hash: 030eed8c5519d44a69b3b458cf5169086852ae0d
|
|
repo: openstack/congress
|
|
version: 9.0.0.0rc1
|
|
- projects:
|
|
- hash: 4977fe3dacbf4de25e8568141d9bdbf7363a5288
|
|
repo: openstack/congress
|
|
version: 9.0.0.0rc2
|
|
- diff-start: 8.0.0
|
|
projects:
|
|
- hash: 4977fe3dacbf4de25e8568141d9bdbf7363a5288
|
|
repo: openstack/congress
|
|
version: 9.0.0
|
|
- version: stein-em
|
|
projects:
|
|
- repo: openstack/congress
|
|
hash: 4977fe3dacbf4de25e8568141d9bdbf7363a5288
|
|
- version: stein-eol
|
|
projects:
|
|
- repo: openstack/congress
|
|
hash: b565c87d0224abb76d3710a4238df433f75ffbf3
|
|
branches:
|
|
- location: 9.0.0.0rc1
|
|
name: stable/stein
|
|
cycle-highlights:
|
|
- Important new NFV fault management capabilities through the addition
|
|
of multiple new features in Congress integration with Nova, Tacker,
|
|
and Monasca.
|
|
- The new JGress framework unlocks whole new classes of policy use
|
|
by making the state of the cloud as given by JSON APIs available
|
|
for policy evaluation. By adopting a JSON query language for expressing
|
|
policy directly over JSON API data, JGress enables deployers to
|
|
plug-in new data sources without being limited by the availability
|
|
of integration drivers.
|
|
- As with every release, we continue to make Congress more robust
|
|
and stable than ever with bug fixes and internal improvements.
|
|
release-notes: https://docs.openstack.org/releasenotes/congress/stein.html
|