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: I6c7134215e06ec3099b02813e11d09cf8a0861e3
This creates the stable/wallaby branch for all client and non-client
libraries
now that we are past the lib freeze on March 11.
If a team wants to wait for a specific patch to make it to the library,
someone from the 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 19.
Change-Id: I4c8f8aabd952c275362ba0ba369b6e82f4518ec6
This is the Wallaby milestone-2 release for python-masakariclient.
Clients and libraries following the cycle-with-intermediary release
model are encouraged to release each milestone to make sure updates
are made available.
If you are happy with the current release hash, please +1 this patch
and we will process a release. If you need to get some important
changes merged first, leave a -1 and update the patch with a new
commit hash to use once it is ready.
If a release is definitely not wanted at this time, please -1 and
leave a comment explaining that and we can abandon the patch.
Any patches with no response will be assumed to be OK and will be
processed by January 21.
Signed-off-by: Hervé Beraud <hberaud@redhat.com>
Change-Id: I4e78ad50f7b55ee1e3f5de382eab75c7c5b7dd67
This is a library release for python-masakariclient for the wallaby-1
milestone. This repo includes commits that have not been releases for
this cycle yet.
If the team is ready to process with this release, please leave a +1
to indicate we should go ahead with the release.
If the team needs more time for things about to merge, or if there is
some other reason a release should not be done at this time, please
leave a -1 with a comment indicating the status. Then update the patch
with the new commit hash to use once the team is ready to do the
release.
Change-Id: I125f0286d21481ea071454ba3fff85ec13ba0451