releases/deliverables/antelope/python-cyborgclient.yaml

---
include-pypi-link: true
storyboard: openstack/cyborg
release-model: cycle-with-intermediary
team: cyborg
type: client-library
repository-settings:
  openstack/python-cyborgclient: {}
releases:
  - version: 2.1.0
    projects:
      - repo: openstack/python-cyborgclient
        hash: 491b85e9a64eeca89b30ae35da5f887e0042a7e3
branches:
  - name: stable/2023.1
    location: 2.1.0
Add 2023.1 Antelope deliverable files The generated content initializes the 2023.1 Antelope cycle's deliverable files based on Zed deliverables. Change-Id: I7ed646e43002084aa791483e56046d94762fff75 2022-10-06 14:32:18 +02:00			`---`
			`include-pypi-link: true`
			`storyboard: openstack/cyborg`
			`release-model: cycle-with-intermediary`
			`team: cyborg`
			`type: client-library`
			`repository-settings:`
			`openstack/python-cyborgclient: {}`
Release final python-cyborgclient for Antelope This is a release for python-cyborgclient to get any merged but unreleased changes out prior to the client lib freeze for Antelope 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 Friday, February 17th. $ git log --oneline --no-merges 2.0.0..491b85e 491b85e Use py3 as the default runtime for tox 83ced8f Switch to 2023.1 Python3 unit tests and generic template name 4f44558 Update master for stable/zed Signed-off-by: Hervé Beraud <hberaud@redhat.com> Change-Id: I95195a8bd9e0cf2758425aeb98e15aed14440ebe 2023-02-13 11:03:57 +01:00			`releases:`
			`- version: 2.1.0`
			`projects:`
			`- repo: openstack/python-cyborgclient`
			`hash: 491b85e9a64eeca89b30ae35da5f887e0042a7e3`
[cyborg] Create 2023.1 branch for client and non-client libs This creates the stable/2023.1 branch for all client and non-client libraries now that we are past the library freeze. If the team wants to wait for a specific patch to make it to the library (for example if the gate of the deliverable is broken and needs to be fixed before branching), then 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, February 24th. Change-Id: I32d1335b09185d37c72055cc91101e0dda995534 2023-02-20 18:49:16 +01:00			`branches:`
			`- name: stable/2023.1`
			`location: 2.1.0`