Entering freeze for libvirt-6.8.0
I have just tagged v6.8.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 Thu, 2020-09-24 at 15:13 +0200, Jiri Denemark wrote:
I have just tagged v6.8.0-rc1 in the repository and pushed signed tarballs and source RPMs to https://libvirt.org/sources/
Can we please stop generating and publishing the source RPMs? They're of little use considering that you can easily run $ rpmbuild -ta libvirt-x.y.z.tar.xz to obtain RPMs from a release archive, so all they really do is clutter the directory listing.
If you have not done so yet, please update NEWS.rst to document any significant change you made since the last release.
Yes, please do that everybody :) -- Andrea Bolognani / Red Hat / Virtualization
On Thu, Sep 24, 2020 at 18:38:18 +0200, Andrea Bolognani wrote:
On Thu, 2020-09-24 at 15:13 +0200, Jiri Denemark wrote:
I have just tagged v6.8.0-rc1 in the repository and pushed signed tarballs and source RPMs to https://libvirt.org/sources/
Can we please stop generating and publishing the source RPMs? They're of little use considering that you can easily run
$ rpmbuild -ta libvirt-x.y.z.tar.xz
to obtain RPMs from a release archive, so all they really do is clutter the directory listing.
The nice thing about the source RPMs is that they are internally signed (in contrast to an external signature in *.asc for tarballs). Personally I don't find them useful either, but some people may think otherwise and I'm not sure they will raise their voice here. We could just stop creating source RPMs and wait if anyone complains. Or we could be a little bit more conservative and just move them to a subdirectory perhaps. I don't mind either way. Jirka
I have just tagged v6.8.0-rc2 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 (2)
-
Andrea Bolognani -
Jiri Denemark