Hi, I tried on IRC but it didn't work out. I realised the other day that I still need an os-traits release for the sound and USB traits that I added a while ago in support of my VDI work. I need those to land before I can really do much more in Nova with the VDI patches. I looked at proposing a release myself, but I couldn't find any documentation on how to actually run the tools for a release independent release. So... Either are there docs on how to do that thing, or could someone do it for me? Thanks, Michael
On 13/05/2025 21:09, Michael Still wrote:
Hi,
I tried on IRC but it didn't work out.
I realised the other day that I still need an os-traits release for the sound and USB traits that I added a while ago in support of my VDI work. I need those to land before I can really do much more in Nova with the VDI patches. I looked at proposing a release myself, but I couldn't find any documentation on how to actually run the tools for a release independent release. So...
the docs are basiclly here https://github.com/openstack/releases/blob/master/doc/source/reference/using... there is a tox command to automate it https://github.com/openstack/releases/blob/master/doc/source/reference/using... but all that going to do for you is adde 4 lines to https://github.com/openstack/releases/blob/master/deliverables/_independent/... so if you want to do that by hand the most recent release is ``` - version: 3.4.0 projects: - repo: openstack/os-traits hash: 45f208b9a09e11155e5acbcf25d90916b0965c05 ``` so for 3.5.0 add ``` - version: 3.5.0 projects: - repo: openstack/os-traits hash: <currnet master git sha> ``` the current tip of master is https://opendev.org/openstack/os-traits/commit/45bc9b800f383780c9ff6519f4ebb... so that would be ``` - version: 3.5.0 projects: - repo: openstack/os-traits hash: 45bc9b800f383780c9ff6519f4ebb48afa5ac546 ``` you can take a look at the most recent release of os-traits for an example https://github.com/openstack/releases/commit/b7b7f10623a016c710b166c71b46413... once the patch merges its will automaticly be build and published ot pypi and then a parch to the requirements repo will be generate by the bot like this https://github.com/openstack/requirements/commit/aea4bdb03846d4b08c0b3decf0e... once that is merged it will be available for all jobs to use.
Either are there docs on how to do that thing, or could someone do it for me?
Thanks, Michael
participants (2)
-
Michael Still
-
Sean Mooney