From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:59689) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1csPfN-0000nZ-H0 for qemu-devel@nongnu.org; Mon, 27 Mar 2017 04:06:18 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1csPfK-00080J-CS for qemu-devel@nongnu.org; Mon, 27 Mar 2017 04:06:17 -0400 Received: from mx1.redhat.com ([209.132.183.28]:44698) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1csPfK-0007zM-6h for qemu-devel@nongnu.org; Mon, 27 Mar 2017 04:06:14 -0400 Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.phx2.redhat.com [10.5.11.15]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 1C7EE3DBD4 for ; Mon, 27 Mar 2017 08:06:13 +0000 (UTC) References: <3d1c16a1-ec05-0367-e569-64a63b34f2e3@redhat.com> <4a56f716-3528-ddd4-f8c4-f3f6b23c469a@redhat.com> From: Thomas Huth Message-ID: Date: Mon, 27 Mar 2017 10:06:09 +0200 MIME-Version: 1.0 In-Reply-To: <4a56f716-3528-ddd4-f8c4-f3f6b23c469a@redhat.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] What's the next QEMU version after 2.9 ? (or: when is a good point in time to get rid of old interfaces) List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: John Snow , qemu-devel@nongnu.org On 24.03.2017 23:10, John Snow wrote: > > > On 03/08/2017 03:26 AM, Thomas Huth wrote: >> >> Hi everybody, >> >> what will be the next version of QEMU after 2.9? Will we go for a 2.10 >> (as I've seen it mentioned a couple of times on the mailing list >> already), or do we dare to switch to 3.0 instead? >> >> I personally dislike two-digit minor version numbers like 2.10 since the >> non-experienced users sometimes mix it up with 2.1 ... and there have >> been a couple of new cool features in the past releases that would >> justify a 3.0 now, too, I think. >> >> But anyway, the more important thing that keeps me concerned is: Someone >> once told me that we should get rid of old parameters and interfaces >> (like HMP commands) primarily only when we're changing to a new major >> version number. As you all know, QEMU has a lot of legacy options, which >> are likely rather confusing than helpful for the new users nowadays, >> e.g. things like the "-net channel" option (which is fortunately even >> hardly documented), but maybe also even the whole vlan/hub concept in >> the net code, or legacy parameters like "-usbdevice". If we switch to >> version 3.0, could we agree to remove at least some of them? >> >> Thomas >> > > As others have stated, we need a few releases to deprecate things first. > > Maybe we should develop a serious plan to develop some of our legacy > interfaces first. > > Maybe 2.10 can introduce a list of things we want to deprecate, > 2.11 can be the transition release, > and then 3.0 can cut the cord and free of us our terrible burden? > > I have a list of things I want to axe... I've started a Wiki page with such a list here: http://wiki.qemu-project.org/Features/LegacyRemoval Feel free to amend! Thomas