[libvirt] Plan for next release
We are getting close to the end of the month, so we may need to freeze next Monday or Tuesday. Are we ready for 1.3.0 now :-) ? I see that configure.ac targets 1.2.18, so a priori no, but would rather have a clear answer :-) Thanks, Daniel -- Daniel Veillard | Open Source and Standards, Red Hat veillard@redhat.com | libxml Gnome XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | virtualization library http://libvirt.org/
On 07/22/2015 11:50 AM, Daniel Veillard wrote:
We are getting close to the end of the month, so we may need to freeze next Monday or Tuesday. Are we ready for 1.3.0 now :-) ? I see that configure.ac targets 1.2.18, so a priori no, but would rather have a clear answer :-)
I had posted patches with "1.3.0" in the docs changes, but haven't pushed them yet (no reviews :-( )
On Wed, Jul 22, 2015 at 12:08:46PM -0400, Laine Stump wrote:
On 07/22/2015 11:50 AM, Daniel Veillard wrote:
We are getting close to the end of the month, so we may need to freeze next Monday or Tuesday. Are we ready for 1.3.0 now :-) ? I see that configure.ac targets 1.2.18, so a priori no, but would rather have a clear answer :-)
Unfortunately we don't. We're trying to achieve clean and extensible design that we're not going to regret (or at least as late as possible).
I had posted patches with "1.3.0" in the docs changes, but haven't pushed them yet (no reviews :-( )
I'll have a look at them today, but be prepared to change that to 1.2.18 :) Martin
-- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
On Wed, 2015-07-22 at 23:50 +0800, Daniel Veillard wrote:
We are getting close to the end of the month, so we may need to freeze next Monday or Tuesday.
I guess a requirement for freeze, or at least for release, is deciding how we want to handle symlinks with long paths[1] so that we can, you know, make dist :) Cheers. [1] https://www.redhat.com/archives/libvir-list/2015-July/msg00869.html -- Andrea Bolognani Software Engineer - Virtualization Team
On Fri, Jul 24, 2015 at 01:28:51PM +0200, Andrea Bolognani wrote:
On Wed, 2015-07-22 at 23:50 +0800, Daniel Veillard wrote:
We are getting close to the end of the month, so we may need to freeze next Monday or Tuesday.
I guess a requirement for freeze, or at least for release, is deciding how we want to handle symlinks with long paths[1] so that we can, you know, make dist :)
Cheers.
[1] https://www.redhat.com/archives/libvir-list/2015-July/msg00869.html
Saw that, and IMHO we need to fix the filename :-) Daniel -- Daniel Veillard | Open Source and Standards, Red Hat veillard@redhat.com | libxml Gnome XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | virtualization library http://libvirt.org/
On 07/24/2015 07:28 AM, Andrea Bolognani wrote:
We are getting close to the end of the month, so we may need to freeze next Monday or Tuesday. I guess a requirement for freeze, or at least for release, is deciding how we want to handle symlinks with long paths[1] so
On Wed, 2015-07-22 at 23:50 +0800, Daniel Veillard wrote: that we can, you know, make dist :)
It needs to be fixed far before the release - make rpm is broken too, and that's my preferred method of testing. I've fixed it locally with a patch to change "deconfigured-cpus" to "down-cpus", but didn't want to push it unilaterally, even though the build is broken.
On Fri, 2015-07-24 at 09:35 -0400, Laine Stump wrote:
On 07/24/2015 07:28 AM, Andrea Bolognani wrote:
We are getting close to the end of the month, so we may need to
freeze next Monday or Tuesday. I guess a requirement for freeze, or at least for release, is deciding how we want to handle symlinks with long paths[1] so
On Wed, 2015-07-22 at 23:50 +0800, Daniel Veillard wrote: that we can, you know, make dist :)
It needs to be fixed far before the release - make rpm is broken too, and that's my preferred method of testing.
I've fixed it locally with a patch to change "deconfigured-cpus" to "down-cpus", but didn't want to push it unilaterally, even though the build is broken.
I just sent a patch renaming it to "nonpresent", which is still short enough not to run into the lenght limit. It's certainly going to be stuck in the moderation queue, so if you have the permissions to do so please let it through :) Cheers. -- Andrea Bolognani Software Engineer - Virtualization Team
participants (4)
-
Andrea Bolognani -
Daniel Veillard -
Laine Stump -
Martin Kletzander