This transition the victoria branch to extended maintenance.
Changes for bugfixes and things the team deems important are
still encouraged, but there will no longer be official releases
off of the branch.
Please +1 if the team is ready for us to proceed with this
transition, or -1 if there are any final backports currently in
flight that we should wait for. For the latter case, please
update the patch with the new commit hash after doing a final
release to get those changes out so we know to proceed with the
transition.
The transition deadline is April 27th, 2022.
Change-Id: I7ae96e80344ddacbbfe136a0e0e3b667af3fba9a
This generated patch adds missing victoria release note page link if
that page exists for a deliverable.
If any of your deliverables does not have a release note link added in
this patch, then please check whether there is an open patch on that
repository with the topic "reno-victoria" [1] still waiting to be
approved.
[1] https://review.opendev.org/q/topic:reno-victoria
Change-Id: I1463846c53d70cb845be2b278be55f6934c6ce77
This release picks up new commits to kolla-ansible since
the last release from stable/victoria.
This is being proposed as a convenience to help make sure stable
changes are being released. If the team is good with this going out,
please respond with a +1 to let the release team know it is OK to
proceed.
If it is not wanted at this time, or if there are more changes that
would be good to get merged before doing a stable release, please
leave a -1 with a comment with what the team would prefer. We can
then either abandon this patch, or wait for an update with a new
commit hash to use instead.
$ git log --oneline --no-merges 11.2.0..5b31b52f7
1c510c33e [CI] [to-revert] Avoid upgrades on CentOS Stream 8
69b7bb93f Fix permission denied errors with ping on c8s
e80acd625 Add logrotate to libvirt service
1dd2e4f3d Access to zun container fails when tls_external enabled.
153fa1ad6 Add logrotate configuration for placement service
cb73051bc rabbitmq: enable/disable prometheus plugin follow up
f67a1d1ec docs: adjust to current defaults
46544622e Support enable/disable rabbitmq prometheus plugins
1a87ed1a0 CI: check-logs - add another exception
145e64d5c Move project_name and kolla_role_name to role vars
c257359dc [CI] Stop testing non-stream CentOS
d5fe6a38c horizon: move horizon_enable_tls_backend to group_vars
b97372923 Add ironic-inspector policy configuration
f14caa1e6 Add ovn_sb_connection to octavia.conf
fe1e6b465 Fix aodh wsgi config file in Debuntu binary
dc5f3700f Register resources info for octavia upgrading
Signed-off-by: Elod Illes <elod.illes@est.tech>
Change-Id: I7f5c22aba1a42a853c0a662a48df84fe4d7f66a8
Cycle-trailing deliverables are regular cycle-following deliverables,
using RCs or not not using RCs -- they just have a different deadline.
Rather than using a release model, those deadline variants are better
described using deliverable types, in much the same way 'library'
deliverables have a specific deadline too.
This simplifies the list of models significantly, and allows to have
proposer validation of trailing deliverables that use RCs or not use
RCs.
For compatibility in old branches, setting 'cycle-trailing' is still
supported, it will just overload the type to 'trailing' if specified.
Change-Id: Ifce88ef3e5dd406f45f25214699f16e736ad5377