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: I61a81ab4b889c96044629b55887c595407e9e448
This tags the final release for all cycle-with-rc projects for Wallaby.
While not required, having PTLs ack this patch would be nice to include
that record in the merged metadata.
Release activity should now be frozen until this is processed on Apr 14.
Any bugfixes merged to stable/wallaby can be queued up and ready to go
as a follow on stable release after the coordinated release date.
There are different diff-start values for each project. This is used
when generating release notes to denote the point where the
stable/victoria branch started to diverge from what is included on
stable/wallaby. For some, this will be the final Victoria major version,
but if multiple RCs were done, this may show the initial RC1 release
version. This is normal.
Change-Id: Ia6d79df224a792915976864857fe2271e031b54d
If you wants to wait for a specific patch to make it to the release,
someone from your team can -1 the patch to have it held, or update that patch
with a different commit SHA.
Patches with no response will be merged by Friday March 26.
$ git log --oneline --no-merges 6.0.0..7d481ad
7d481ad Fix another base64 python3 issue
3c41b4f Fix base64 usage for Python 3
dd11311 Add Python3 wallaby unit tests
432be0d Update master for stable/victoria
Signed-off-by: Hervé Beraud <hberaud@redhat.com>
Change-Id: Id287b1558ded57c978f6f5a0dab2473c0dfa2069