From: Eric Blake <eblake@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>,
"Stefan Hajnoczi" <stefanha@redhat.com>
Cc: libvir-list@redhat.com, Peter Maydell <peter.maydell@linaro.org>,
philmd@redhat.com, qemu-devel@nongnu.org
Subject: Re: [PATCH] docs/system: clarify deprecation scheduled
Date: Mon, 14 Sep 2020 09:32:11 -0500 [thread overview]
Message-ID: <5ccbee6a-cbf7-d790-457f-b15c3eef5c1e@redhat.com> (raw)
In-Reply-To: <20200914142146.GN1252186@redhat.com>
On 9/14/20 9:21 AM, Daniel P. Berrangé wrote:
> On Tue, Aug 11, 2020 at 11:47:36AM +0100, Stefan Hajnoczi wrote:
>> 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.
>>
> So we're changing
>
> The feature will remain functional for 2 releases prior to actual removal.
>
> to
>
> The feature will remain functional for 1 more release after deprecation.
>
> How about
>
> 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.
Longer, but definitely conveys more information in an
easier-to-understand format.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
next prev parent reply other threads:[~2020-09-14 14:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-11 10:47 [PATCH] docs/system: clarify deprecation scheduled Stefan Hajnoczi
2020-09-14 13:46 ` Stefan Hajnoczi
2020-09-14 14:21 ` Daniel P. Berrangé
2020-09-14 14:32 ` Eric Blake [this message]
2020-09-14 14:35 ` Peter Maydell
2020-09-15 15:10 ` Stefan Hajnoczi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5ccbee6a-cbf7-d790-457f-b15c3eef5c1e@redhat.com \
--to=eblake@redhat.com \
--cc=berrange@redhat.com \
--cc=libvir-list@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).