As a courtesy for project teams, on RC1 week the release management team proposes a RC1 release for all cycle-with-rc deliverables, based on HEAD. That RC1 will double as the branch point for the stable/victoria branch for kuryr-kubernetes. Release liaison or PTL should +1 this proposal if they are happy with it, amend this proposal (for example with a more recent SHA) to match their needs, or -1 to block it until release-critical issues are all fixed. Change-Id: Ifa65f09c6a67f35f5a49b05e913ee6f4895b9c04 Signed-off-by: Thierry Carrez <thierry@openstack.org>
25 lines
709 B
YAML
25 lines
709 B
YAML
---
|
|
launchpad: kuryr-kubernetes
|
|
release-model: cycle-with-rc
|
|
team: kuryr
|
|
type: other
|
|
repository-settings:
|
|
openstack/kuryr-kubernetes: {}
|
|
cycle-highlights:
|
|
- |
|
|
Kuryr will no longer use annotations to store data about OpenStack objects
|
|
in K8s API. Instead a corresponding CRDs are created, i.e. KuryrPort,
|
|
KuryrLoadBalancer and KuryrNetworkPolicy.
|
|
- |
|
|
Logs on INFO level should be much cleaner now.
|
|
- |
|
|
Added support for autodetection of VM bridging interface in nested setups.
|
|
releases:
|
|
- version: 3.0.0.0rc1
|
|
projects:
|
|
- repo: openstack/kuryr-kubernetes
|
|
hash: ff0299d5074c13fe87bd69948837ba1358ad1ea7
|
|
branches:
|
|
- name: stable/victoria
|
|
location: 3.0.0.0rc1
|