From nobody Wed May 1 05:20:03 2024 Delivered-To: importer@patchew.org Received-SPF: pass (zohomail.com: domain of redhat.com designates 205.139.110.120 as permitted sender) client-ip=205.139.110.120; envelope-from=libvir-list-bounces@redhat.com; helo=us-smtp-1.mimecast.com; Authentication-Results: mx.zohomail.com; dkim=pass; spf=pass (zohomail.com: domain of redhat.com designates 205.139.110.120 as permitted sender) smtp.mailfrom=libvir-list-bounces@redhat.com; dmarc=pass(p=none dis=none) header.from=redhat.com ARC-Seal: i=1; a=rsa-sha256; t=1597142880; cv=none; d=zohomail.com; s=zohoarc; b=agrEMQaTYQf/70lyFEUlIdkHDozfboBOCELVY2S39EfDkPte2Lg0YSmq5QW+wuBjg+Gv1XzFmDyICpueqjMuZ6B2k3RNg+azQQklG/tftWqdI3oEHEwtqij1C7QUeHy1aX8mO2D6xv6xmSoa1yCf1M7JLtjOKXLnXSWaTp6Lxhg= ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=zohomail.com; s=zohoarc; t=1597142880; h=Content-Type:Content-Transfer-Encoding:Cc:Date:From:List-Subscribe:List-Post:List-Id:List-Archive:List-Help:List-Unsubscribe:MIME-Version:Message-ID:Sender:Subject:To; bh=Dt48sDSWlxZB9QQPIaHBPpb/bwOEKoiFUS77UHsynYE=; b=h2tb/ydMMekVAaGivaQ14WmeEa/Yz2zL5U3gvDc9m+Swck0yAI8oHOSIvG+i//Mob6ccPYKNn3QhJt68OHMfj47DDZD8sbsoNdVw06FErCD9wIHZbI+T97VGG44OMGT9NGLFXKQGtnvSKrntLbpNwbuaeHv5pFfsNvWp683FW5I= ARC-Authentication-Results: i=1; mx.zohomail.com; dkim=pass; spf=pass (zohomail.com: domain of redhat.com designates 205.139.110.120 as permitted sender) smtp.mailfrom=libvir-list-bounces@redhat.com; dmarc=pass header.from= (p=none dis=none) header.from= Return-Path: Received: from us-smtp-1.mimecast.com (us-smtp-delivery-1.mimecast.com [205.139.110.120]) by mx.zohomail.com with SMTPS id 1597142880969601.8928539959193; Tue, 11 Aug 2020 03:48:00 -0700 (PDT) Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-34-qOaQIQLjPX6k0pj-uabWCQ-1; Tue, 11 Aug 2020 06:47:56 -0400 Received: from smtp.corp.redhat.com (int-mx08.intmail.prod.int.phx2.redhat.com [10.5.11.23]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 672B7101C8A6; Tue, 11 Aug 2020 10:47:51 +0000 (UTC) Received: from colo-mx.corp.redhat.com (colo-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.20]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 9BDB31A836; Tue, 11 Aug 2020 10:47:49 +0000 (UTC) Received: from lists01.pubmisc.prod.ext.phx2.redhat.com (lists01.pubmisc.prod.ext.phx2.redhat.com [10.5.19.33]) by colo-mx.corp.redhat.com (Postfix) with ESMTP id BF1B51809554; Tue, 11 Aug 2020 10:47:45 +0000 (UTC) Received: from smtp.corp.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) by lists01.pubmisc.prod.ext.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id 07BAlidD021996 for ; Tue, 11 Aug 2020 06:47:44 -0400 Received: by smtp.corp.redhat.com (Postfix) id 19D7E6F130; Tue, 11 Aug 2020 10:47:44 +0000 (UTC) Received: from localhost (ovpn-114-81.ams2.redhat.com [10.36.114.81]) by smtp.corp.redhat.com (Postfix) with ESMTP id CDA586F12F; Tue, 11 Aug 2020 10:47:37 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1597142879; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding:list-id:list-help: list-unsubscribe:list-subscribe:list-post; bh=Dt48sDSWlxZB9QQPIaHBPpb/bwOEKoiFUS77UHsynYE=; b=RP44oIjQifC9GU9g2aY5xGO8EXs9QVxQNdq9GTnN78vtvqfK1UTUhj1+kojA8amtNEdJM+ INWE5DSQgF+8Ztzj/5ezFdNKYFU4Eb0AMRXqN0ELy9tBPViOe71Daf02JDMMd7Hk/i1mr5 JXRc4WAE+oSrxFR3B3Wokxo0vRG8XqI= X-MC-Unique: qOaQIQLjPX6k0pj-uabWCQ-1 From: Stefan Hajnoczi To: qemu-devel@nongnu.org Subject: [PATCH] docs/system: clarify deprecation scheduled Date: Tue, 11 Aug 2020 11:47:36 +0100 Message-Id: <20200811104736.17140-1-stefanha@redhat.com> MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.79 on 10.5.11.11 X-loop: libvir-list@redhat.com Cc: libvir-list@redhat.com, philmd@redhat.com, Stefan Hajnoczi , Peter Maydell X-BeenThere: libvir-list@redhat.com X-Mailman-Version: 2.1.12 Precedence: junk List-Id: Development discussions about the libvirt library & tools List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: libvir-list-bounces@redhat.com Errors-To: libvir-list-bounces@redhat.com X-Scanned-By: MIMEDefang 2.84 on 10.5.11.23 Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=libvir-list-bounces@redhat.com X-Mimecast-Spam-Score: 0.001 X-Mimecast-Originator: redhat.com Content-Transfer-Encoding: quoted-printable X-ZohoMail-DKIM: pass (identity @redhat.com) Content-Type: text/plain; charset="utf-8" The sentence explaining the deprecation schedule is ambiguous. Make it clear that a feature deprecated in the Nth release is guaranteed to remain available in the N+1th release. Removal can occur in the N+2nd release or later. As an example of this in action, see commit 25956af3fe5dd0385ad8017bc768a6afe41e2a74 ("block: Finish deprecation of 'qemu-img convert -n -o'"). The feature was deprecated in QEMU 4.2.0. It was present in the 5.0.0 release and removed in the 5.1.0 release. Signed-off-by: Stefan Hajnoczi --- docs/system/deprecated.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/system/deprecated.rst b/docs/system/deprecated.rst index 851dbdeb8a..fecfb2f1c1 100644 --- a/docs/system/deprecated.rst +++ b/docs/system/deprecated.rst @@ -4,9 +4,9 @@ Deprecated features In general features are intended to be supported indefinitely once introduced into QEMU. In the event that a feature needs to be removed, it will be listed in this section. The feature will remain functional -for 2 releases prior to actual removal. Deprecated features may also -generate warnings on the console when QEMU starts up, or if activated -via a monitor command, however, this is not a mandatory requirement. +for 1 more release after deprecation. Deprecated features may also generate +warnings on the console when QEMU starts up, or if activated via a monitor +command, however, this is not a mandatory requirement. =20 Prior to the 2.10.0 release there was no official policy on how long features would be deprecated prior to their removal, nor --=20 2.26.2