This transition the wallaby 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 November 2nd, 2022.
Change-Id: If2fb9e27942d9f51230ab87a69263b9b04335f3b
This generated patch adds missing wallaby 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-wallaby" [1] still waiting to be
approved.
[1] https://review.opendev.org/q/topic:reno-wallaby
Change-Id: Ie3abb8f841a5990d973956cd5d656829a47f27df
Some deliverables never released the patches related to
the `TOX_CONSTRAINTS_FILE` switch for Wallaby. Not landing
this switch downstream (to distros) became problematic as
tox target executed downstream refered to master's
requirements constraints and so validations started to fail
with downstream usage of Wallaby (OSP17 by example).
So even if deliverables does not provides functional changes
I prefer release them as a bugfix version to fix this kind
of problems for distros.
NOTE: oslo.cache is already at the version 2.8.0 on Xena
so I can't release a minor version even if functional changes
are landed.
Change-Id: I920ee7bcca3cbf3e4051b3a3098beed53b1c969d
This creates the stable/wallaby branch for any non-client libraries
now that we are past the lib freeze on March 11.
Change-Id: Ia6fc6d1965bd80fde4d324d8757a96dc383a19f6