[PATCH] docs/system: clarify deprecation scheduled

Eric Blake eblake at redhat.com
Mon Sep 14 14:32:11 UTC 2020


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




More information about the libvir-list mailing list