This creates the stable/xena branch for all client
and non-client libraries now that we are past the
lib freeze on September 02.
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, September 10.
Change-Id: Iad31b135ab867712aae2f41d32a08dd787216a5f
This proposed a release for python-blazarclient to get any final merged changes
out prior to the lib freeze for Xena going into effect.
If the team is ready to proceed, please leave a +1 to acknowledge this
release and we will process right away. If the team is working on any
final merges, leave a -1 with some detail on the status and update the
patch with the new commit hash to use when ready.
Patches with no response will be merged by Thursday, September 02.
$ git log --oneline --no-merges 3.2.0..d2eb2f6
f2277b5 Add openstackclient support
27c426a Migrate from testr to stestr
c9114b7 Default client service type to reservation
1cf4d73 Add Python3 xena unit tests
c3fef3d Update master for stable/wallaby
a2d8abf Change dashes to underscore in setup.cfg
Signed-off-by: Hervé Beraud <hberaud@redhat.com>
Change-Id: I1aeb8ca05241dfe4c523f6f0d0bc1e3216eaf530
Only few projects have been detected as unreleased during Wallaby:
- deliverables/xena/cinderlib.yaml
- deliverables/xena/release-test.yaml
- deliverables/xena/openstack-ansible-roles.yaml
- deliverables/xena/kolla-ansible.yaml
- deliverables/xena/kayobe.yaml
They are mostly trailing projects, so, at this point they hadn't yet
been released.
Only our testing project remain really undelivered during Wallaby, however,
I decided to keep it around during Xena, either to allow us to test
urgent things or to convert it to JS testing project for example (to
catch the yarn/nodejs issues proactively by example).
Change-Id: I446061df0474ba36e39d44a4a70017b742856c11
