From nobody Fri Mar 29 06:34:16 2024 Delivered-To: importer@patchew.org Received-SPF: pass (zohomail.com: domain of redhat.com designates 63.128.21.124 as permitted sender) client-ip=63.128.21.124; envelope-from=libvir-list-bounces@redhat.com; helo=us-smtp-delivery-124.mimecast.com; Authentication-Results: mx.zohomail.com; dkim=pass; spf=pass (zohomail.com: domain of redhat.com designates 63.128.21.124 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=1600182597; cv=none; d=zohomail.com; s=zohoarc; b=LGzNojfujitYEFS6+9CxZsjY3tyDIzYZ1Wijext/jc4C722IrIsTyoUzdoCeRxjv/hN4As8eV4qyN8QaPWPfyYUBh839J3o2EPAl2VQaN6DBsZL1td6n2PF3doaUlFBaNC3tOLOWZbQ482dSAkqN+3SxbJTN0tPi7RRFzRb3y7k= ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=zohomail.com; s=zohoarc; t=1600182597; 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=3PpilwqKCUqIAPlHJZeQDx1hYmxCvoXCnGFvE6o8Xnc=; b=Z2Imu0VOfwKmakLBAT9tC/dG6QuTvqt0vSZ9FfL8Spgs95zPS2s659p70Rd8GoycRn/dRDJf4155ZEdJH/5cdRtkXgbZa0DpUvCHQGAJf/8IieX+82ack3UTGjgBKoMSMHEWH96+3HIVdcTyB+LL6csJrRsxnAXdMRRIp6I2Np8= ARC-Authentication-Results: i=1; mx.zohomail.com; dkim=pass; spf=pass (zohomail.com: domain of redhat.com designates 63.128.21.124 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-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [63.128.21.124]) by mx.zohomail.com with SMTPS id 160018259760951.86152614965113; Tue, 15 Sep 2020 08:09:57 -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-224-yBp8PqSoOByzm4fXV5zzwQ-1; Tue, 15 Sep 2020 11:09:49 -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 mimecast-mx01.redhat.com (Postfix) with ESMTPS id C650A801ABA; Tue, 15 Sep 2020 15:09:21 +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 9038375138; Tue, 15 Sep 2020 15:09:19 +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 DDA17183D022; Tue, 15 Sep 2020 15:09:14 +0000 (UTC) Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.phx2.redhat.com [10.5.11.22]) by lists01.pubmisc.prod.ext.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id 08FF9D7f017981 for ; Tue, 15 Sep 2020 11:09:13 -0400 Received: by smtp.corp.redhat.com (Postfix) id 41FC81002D53; Tue, 15 Sep 2020 15:09:13 +0000 (UTC) Received: from localhost (ovpn-113-7.ams2.redhat.com [10.36.113.7]) by smtp.corp.redhat.com (Postfix) with ESMTP id D0C5B10013BD; Tue, 15 Sep 2020 15:09:05 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1600182595; 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=3PpilwqKCUqIAPlHJZeQDx1hYmxCvoXCnGFvE6o8Xnc=; b=YUwWIy2aBpykXSsfOVKW2kBnkZmkAhWxLAyh+wfVgsXDsfYE8cFleTH5DZ0s30ThzMkFbc iRNi/DxYYTTp0Cnj1XEe1JgA6hK+HAStyXw8l8WdL4OUZd1v+e7SyRwf5hcbgIfBBQjmmJ lLEoVYsyZ/J0Xw8k70+9nXBQOfvb6uw= X-MC-Unique: yBp8PqSoOByzm4fXV5zzwQ-1 From: Stefan Hajnoczi To: qemu-devel@nongnu.org Subject: [PATCH v2] docs/system: clarify deprecation schedule Date: Tue, 15 Sep 2020 16:07:34 +0100 Message-Id: <20200915150734.711426-1-stefanha@redhat.com> MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.84 on 10.5.11.22 X-MIME-Autoconverted: from base64 to 8bit by lists01.pubmisc.prod.ext.phx2.redhat.com id 08FF9D7f017981 X-loop: libvir-list@redhat.com Cc: libvir-list@redhat.com, Peter Maydell , philmd@redhat.com, Stefan Hajnoczi 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.79 on 10.5.11.15 Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=libvir-list-bounces@redhat.com X-Mimecast-Spam-Score: 0.002 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-ZohoMail-DKIM: pass (identity @redhat.com) 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. Suggested-by: Daniel P. Berrang=C3=A9 Signed-off-by: Stefan Hajnoczi Reviewed-by: Daniel P. Berrang=C3=A9 Reviewed-by: Philippe Mathieu-Daud=C3=A9 --- v2: * Use Dan's suggested wording [Daniel Berrange] --- docs/system/deprecated.rst | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/docs/system/deprecated.rst b/docs/system/deprecated.rst index 0cb8b01424..f2d5bd8ce1 100644 --- a/docs/system/deprecated.rst +++ b/docs/system/deprecated.rst @@ -3,10 +3,11 @@ Deprecated features =20 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. +it will be listed in this section. The feature will remain functional for = the +release in which it was deprecated and one further release. After these two +releases, the feature is liable to be removed. 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