Entering freeze for libvirt-9.0.0
I have just tagged v9.0.0-rc1 in the repository and pushed signed tarballs and source RPMs to https://libvirt.org/sources/ Please give the release candidate some testing and in case you find a serious issue which should have a fix in the upcoming release, feel free to reply to this thread to make sure the issue is more visible. If you have not done so yet, please update NEWS.rst to document any significant change you made since the last release. Thanks, Jirka
On Tue, Jan 10, 2023 at 09:28:22AM +0100, Jiri Denemark wrote:
I have just tagged v9.0.0-rc1 in the repository and pushed signed tarballs and source RPMs to https://libvirt.org/sources/
Please give the release candidate some testing and in case you find a serious issue which should have a fix in the upcoming release, feel free to reply to this thread to make sure the issue is more visible.
If you have not done so yet, please update NEWS.rst to document any significant change you made since the last release.
Before we cut the release I'd like us to re-consider one addition of the passt support, which is XML ABI sensitive, as I think the design is a mistake https://listman.redhat.com/archives/libvir-list/2023-January/236998.html With regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
On Tue, Jan 10, 2023 at 09:28:22AM +0100, Jiri Denemark wrote:
I have just tagged v9.0.0-rc1 in the repository and pushed signed tarballs and source RPMs to https://libvirt.org/sources/
Please give the release candidate some testing and in case you find a serious issue which should have a fix in the upcoming release, feel free to reply to this thread to make sure the issue is more visible.
Note we can't release the libvirt-python binding code as it is. It fails to build when pointed to the 9.0.0-rc1 C library, since the code generator can't cope with virDomainFDAssociate. With regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
On Wed, Jan 11, 2023 at 18:47:22 +0000, Daniel P. Berrangé wrote:
On Tue, Jan 10, 2023 at 09:28:22AM +0100, Jiri Denemark wrote:
I have just tagged v9.0.0-rc1 in the repository and pushed signed tarballs and source RPMs to https://libvirt.org/sources/
Please give the release candidate some testing and in case you find a serious issue which should have a fix in the upcoming release, feel free to reply to this thread to make sure the issue is more visible.
Note we can't release the libvirt-python binding code as it is. It fails to build when pointed to the 9.0.0-rc1 C library, since the code generator can't cope with virDomainFDAssociate.
Oops, I'll write the override.
On Thu, Jan 12, 2023 at 10:51:55AM +0100, Peter Krempa wrote:
On Wed, Jan 11, 2023 at 18:47:22 +0000, Daniel P. Berrangé wrote:
On Tue, Jan 10, 2023 at 09:28:22AM +0100, Jiri Denemark wrote:
I have just tagged v9.0.0-rc1 in the repository and pushed signed tarballs and source RPMs to https://libvirt.org/sources/
Please give the release candidate some testing and in case you find a serious issue which should have a fix in the upcoming release, feel free to reply to this thread to make sure the issue is more visible.
Note we can't release the libvirt-python binding code as it is. It fails to build when pointed to the 9.0.0-rc1 C library, since the code generator can't cope with virDomainFDAssociate.
Oops, I'll write the override.
Peter's merge request for this is now in master, so we're good for release on the python front. I've got similar MRs open for go/perl With regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
I have just tagged v9.0.0-rc2 (the last minute change to the XML format for passt is included) in the repository and pushed signed tarballs and source RPMs to https://libvirt.org/sources/ Please give the release candidate some testing and in case you find a serious issue which should have a fix in the upcoming release, feel free to reply to this thread to make sure the issue is more visible. If you have not done so yet, please update NEWS.rst to document any significant change you made since the last release. Thanks, Jirka
participants (3)
-
Daniel P. Berrangé -
Jiri Denemark -
Peter Krempa