If we want to land a release on Mon Dec 2, I would suggest entering freeze next week. The amount of patches since 1.1.4 is not very large so we could start the freeze say on Wed 27, but IMHO it all depennds if Dan patches about splitting out the python bindings gets in for that release. If yes I would probably prefer to freeze one more day (start Tues 26), and bump release name to 1.2.0 as this is a significant change from an user perspective, otherwise 1.1.5 and freeze next Wed. Opinions ? Dan do you think you can/want to land this set in the coming week ?

On Nov 18, 2013, at 8:09 PM, Daniel Veillard <veillard(a)redhat.com&gt; wrote: If we want to land a release on Mon Dec 2, I would suggest entering freeze next week. The amount of patches since 1.1.4 is not very large so we could start the freeze say on Wed 27, but IMHO it all depennds if Dan patches about splitting out the python bindings gets in for that release. If yes I would probably prefer to freeze one more day (start Tues 26), and bump release name to 1.2.0 as this is a significant change from an user perspective, otherwise 1.1.5 and freeze next Wed. Opinions ? Dan do you think you can/want to land this set in the coming week ?

On Mon, Nov 18, 2013 at 09:46:00PM -0600, Doug Goldstein wrote: > > On Nov 18, 2013, at 8:09 PM, Daniel Veillard <veillard(a)redhat.com&gt; wrote: > > > > If we want to land a release on Mon Dec 2, I would suggest entering > > freeze next week. The amount of patches since 1.1.4 is not very large > > so we could start the freeze say on Wed 27, but IMHO it all depennds if > > Dan patches about splitting out the python bindings gets in for that > > release. If yes I would probably prefer to freeze one more day (start > > Tues 26), and bump release name to 1.2.0 as this is a significant change > > from an user perspective, otherwise 1.1.5 and freeze next Wed. > > > > Opinions ? Dan do you think you can/want to land this set in the > > coming week ? > > > > > See my patch set on the mailing list that completes most of the > remaining items so it should be possible. Obviously it needs a lot of > testing and review, I also did not incorporate Eric's reviews to Dan's > patches yet but it works on Fedora 18 and some other Linuxes so it should > be doable. Yup, saw that, thanks ! I guess we need Dan ACK to push but IMHO the sooner the better, the kind of problems we are gonna find will be with portability and pushing is the best way to get tested :-)

On Tue, Nov 19, 2013 at 03:05:24PM +0000, Daniel P. Berrange wrote: > On Tue, Nov 19, 2013 at 01:13:04PM +0800, Daniel Veillard wrote: > > On Mon, Nov 18, 2013 at 09:46:00PM -0600, Doug Goldstein wrote: > > > > On Nov 18, 2013, at 8:09 PM, Daniel Veillard <veillard(a)redhat.com&gt; wrote: > > > > > > > > If we want to land a release on Mon Dec 2, I would suggest entering > > > > freeze next week. The amount of patches since 1.1.4 is not very large > > > > so we could start the freeze say on Wed 27, but IMHO it all depennds if > > > > Dan patches about splitting out the python bindings gets in for that > > > > release. If yes I would probably prefer to freeze one more day (start > > > > Tues 26), and bump release name to 1.2.0 as this is a significant change > > > > from an user perspective, otherwise 1.1.5 and freeze next Wed. > > > > > > > > Opinions ? Dan do you think you can/want to land this set in the > > > > coming week ? > > > > > > > > > > > See my patch set on the mailing list that completes most of the > > > remaining items so it should be possible. Obviously it needs a lot of > > > testing and review, I also did not incorporate Eric's reviews to Dan's > > > patches yet but it works on Fedora 18 and some other Linuxes so it should > > > be doable. > > > > Yup, saw that, thanks ! I guess we need Dan ACK to push but IMHO the > > sooner the better, the kind of problems we are gonna find will be with > > portability and pushing is the best way to get tested :-) > > Given Doug's work we're probably at a state where we can do a real > release of the separated bindings. We've a little more work to make > python code work with libvirt back to 0.9.6 which is what OpenStack > targets as a min version. We also found we missed moving the > example programs. Those two things should be doable though. > > Agree that we should probably take the chance to bump the version > to 1.2.0 since it is a significant milestone. Okay, so let's get this pushed preferably this week and enter 1.2.0 freeze for next Tuesday 26 Nov,

2013/11/19 11:13 "Daniel Veillard" <veillard(a)redhat.com&gt;: > > If we want to land a release on Mon Dec 2, I would suggest entering > freeze next week. The amount of patches since 1.1.4 is not very large > so we could start the freeze say on Wed 27, but IMHO it all depennds if > Dan patches about splitting out the python bindings gets in for that > release. If yes I would probably prefer to freeze one more day (start > Tues 26), and bump release name to 1.2.0 as this is a significant change > from an user perspective, otherwise 1.1.5 and freeze next Wed. > > Opinions ? Dan do you think you can/want to land this set in the > coming week ? I'm preparing a patch set for VirtualBox 4.3 API support and will send it in this week. Any chance to be included in 1.1.5?