releases/deliverables/queens/congress.yaml
Sean McGinnis 69e65659e9 Update queens release note links
Once more, with feeling.

Change-Id: I1cd0c0c80c28b0299bf649411b9561df4b8ce60b
2018-03-06 22:17:42 -06:00

50 lines
1.8 KiB
YAML

---
launchpad: congress
release-model: cycle-with-milestones
team: congress
type: service
releases:
- version: 7.0.0.0b1
projects:
- repo: openstack/congress
hash: a729a0926dcf3d5fcb8ee5640ea0bb5dec85e1a7
- version: 7.0.0.0b2
projects:
- repo: openstack/congress
hash: 4043745bd48736f9705a0e8b764a1bbe4186793e
- version: 7.0.0.0b3
projects:
- repo: openstack/congress
hash: d9f6b258f7b66b556aef5c919dae0679db2067cf
- version: 7.0.0.0rc1
projects:
- repo: openstack/congress
hash: b15aa16c7f3042a50aa506822867d5c36738e545
- version: 7.0.0.0rc2
projects:
- repo: openstack/congress
hash: f26f54774f598fa41d6fb0b8b01054330b5aee31
- diff-start: 6.0.0
projects:
- repo: openstack/congress
hash: f26f54774f598fa41d6fb0b8b01054330b5aee31
version: 7.0.0
repository-settings:
openstack/congress: {}
branches:
- location: 7.0.0.0rc1
name: stable/queens
cycle-highlights:
- 'Mistral Integration: Congress can now trigger workflows according to operator-defined
policy. From sending emails to running ansible playbooks, Congress and Mistral
can take infrastructure automation and fault-recovery to the next level.'
- 'Config Validation: To help operators catch improper, insecure, or incompatible
configurations across the Stack, the new configuration validation facility enables
Congress to monitor service configurations according to policy.'
- 'Tag-based Security: To help operators secure and manage self-service infrastructure,
Congress now supports enforcement of application-based network security policies
based on tags and other semantic information.'
- 'Bug Fixes: As with every release, we continue to make Congress more robust and
stable than ever.'
release-notes: https://docs.openstack.org/releasenotes/congress/queens.html