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 :) -- Andrea Bolognani / Red Hat / Virtualization
