As planned yesterday (but a bit late) I tagged Release Candidate 1 in git and pushed the signed tarball and rpms to the usual place: ftp://libvirt.org/libvirt/ Seems to work fine in my limited testing, but please give them a try especially for portability accross arches and platforms ! If things go well (and https://ci.centos.org/view/libvirt/ looks good !) then I will push RC2 on Fraiday and get the final 3.10.0 out on Monday, but please give it some testing and report !

On Thu, Nov 30, 2017 at 17:13:02 +0100, Peter Krempa wrote: > On Wed, Nov 29, 2017 at 17:27:40 +0100, Daniel Veillard wrote: > > As planned yesterday (but a bit late) I tagged Release Candidate 1 > > in git and pushed the signed tarball and rpms to the usual place: > > > > ftp://libvirt.org/libvirt/ > > > > > > Seems to work fine in my limited testing, but please give them a try > > especially for portability accross arches and platforms ! > > > > If things go well (and https://ci.centos.org/view/libvirt/ looks good !) > > then I will push RC2 on Fraiday and get the final 3.10.0 out on Monday, > > > > but please give it some testing and report ! > > The release should wait until we settle the discussion dealing with > <shareable/> disks with qcow2 images which is at > > https://bugzilla.redhat.com/show_bug.cgi?id=1518517 > > since the patches were added in this release and thus if we'll opt to > revert them we should do it prior to the release. Daniel pointed out that libguestfs may be using <shareable/> wrong in Comment 17 of that BZ. I think we can go ahead with the release.