On 2/16/22 3:59 AM, Christian Ehrhardt wrote: > On Tue, Jan 25, 2022 at 1:38 PM Andrea Bolognani <abologna@xxxxxxxxxx> wrote: >> >> On Tue, Jan 25, 2022 at 11:21:27AM +0100, Christian Ehrhardt wrote: >>> On Tue, Jan 25, 2022 at 10:33 AM Andrea Bolognani <abologna@xxxxxxxxxx> wrote: >>>> On Mon, Jan 24, 2022 at 03:53:12PM -0500, Cole Robinson wrote: >>>>> On 1/23/22 11:47 AM, Andrea Bolognani wrote: >>>>>> Do you think there's any chance of that happening in the next couple >>>>>> of weeks? >>>>> >>>>> 2 weeks: maybe. 4 weeks: more likely. There's already some potentially >>>>> disruptive stuff in git like feature removals and default changes, but >>>>> there's more coming, and I'd rather they all be in one release than two >>>>> releases in close proximity. I'm actively working on it all though >>>> >>>> That makes perfect sense, and having a rough timeline should make it >>>> possible to plan the Debian work accordingly. Thanks! >>> >>> Thanks to both of you for taking care of this! >>> >>> FYI - Feb 24th is the next Ubuntu feature freeze (just the estimated 4 >>> weeks from now), if we could manage to get it done by then that would >>> be great. >>> Keep me in the loop if we need a feature freeze exception. >> >> Given your deadline, I would probably not hold out for an upstream >> release and coordinate with the Debian developers to make sure a >> 3.2.0-based package that can be built against the latest libvirt >> release is available in the archive instead. You can then decide to >> rebase if the new virt-manager release materializes in time. But >> that's just how *I* would personally handle the situation :) > > I'm not holding breath on anything :-) > But I did the virtual version of it [1] which allows me to wait just a > tiny bit longer. > > Also I wanted to use this opportunity and the fact that since the 2-4 > weeks estimate 3.5 have passed by now. > Therefore @Cole Robinson is there any update on a new release ETA > based on the work so far? > > [1]: https://bugs.launchpad.net/ubuntu/+source/virt-manager/+bug/1961027 All the defaults changes are in git now. If you wanted to push a git snapshot to ubuntu, now is a good time. I'm doing the same for fedora 36 tomorrow. Final release will be next week after some smaller changes. There is one big virt-install defaults change that will cause some previous usage to error: https://listman.redhat.com/archives/virt-tools-list/2022-February/msg00021.html Depending on how close you are to release it might be disruptive to push it, if virt-install is used in distro CI or something. Just something to consider. - Cole
