On Mon, Nov 25, 2019 at 03:45:35PM +0100, Aleksandar Markovic wrote: > On Monday, November 25, 2019, Philippe Mathieu-Daudé <philmd@xxxxxxxxxx> > wrote: > > > The r4k machine was introduced in 2005 (6af0bf9c7) and its last > > logical change was in 2005 (9542611a6). After we can count 164 > > maintenance commits (QEMU API changes) with the exception of > > 1 fix in 2015 (memory leak, commit 3ad9fd5a). > > > > > Please don't start any deprecation process. This requires certain > consultation within my company. Rest assured that everyone's opinion will > be taken into account while doing consiltation. The idea of having a deprecation process is precisely to allow time for people like to provide feedback before any deletion takes place. So this is not a reason to delay starting of deprecation. The process lasts for 2 releases before we delete anything: https://qemu.weilnetz.de/doc/qemu-doc.html#Deprecated-features When we start the clock now, it is deprecated when 5.0 releases in April 2020, and still deprecated with 5.1 in August 2020. The code won't be deleted until Sep 2020 when 5.2 dev cycle opens, and there's still time to undelete it right up until the 5.2 feature freeze in late Oct 2020. That's 11 months away, which is plenty of time for feedback IMHO. Regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :| -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list
