Re: Entering freeze for libvirt-6.9.0
> On Oct 26, 2020, at 2:02 PM, Jiri Denemark wrote: > > I have just tagged v6.9.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. I'm not sure if it's a "serious" issue, since the code does work, but I'd like to see my "Hyper-V code cleanup" patchset make it into 6.9.0. It removes some duplicate functions that I accidentally committed due to the WQL formatting being so different. It also includes some general code cleanup. Thanks! -- Matt
Re: Entering freeze for libvirt-6.9.0
On Mon, Oct 26, 2020 at 2:03 PM Jiri Denemark wrote: > > I have just tagged v6.9.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. > I encountered two basic issues when testing package builds in my pipeline, and have sent patches to the list: * https://www.redhat.com/archives/libvir-list/2020-October/msg01407.html * https://www.redhat.com/archives/libvir-list/2020-October/msg01408.html Those two were the most urgent I discovered with a quick run for my pipeline. -- 真実はいつも一つ！/ Always, there's only one truth!
