All of lore.kernel.org
 help / color / mirror / Atom feed
* [PATCH v2] docs/system: clarify deprecation schedule
@ 2020-09-15 15:07 Stefan Hajnoczi
  2020-09-15 15:28 ` Daniel P. Berrangé
                   ` (2 more replies)
  0 siblings, 3 replies; 4+ messages in thread
From: Stefan Hajnoczi @ 2020-09-15 15:07 UTC (permalink / raw)
  To: qemu-devel
  Cc: libvir-list, Peter Maydell, philmd, Daniel Berrange, Stefan Hajnoczi

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é <berrange@redhat.com>
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
---
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
 
 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.
 
 Prior to the 2.10.0 release there was no official policy on how
 long features would be deprecated prior to their removal, nor
-- 
2.26.2


^ permalink raw reply related	[flat|nested] 4+ messages in thread

* Re: [PATCH v2] docs/system: clarify deprecation schedule
  2020-09-15 15:07 [PATCH v2] docs/system: clarify deprecation schedule Stefan Hajnoczi
@ 2020-09-15 15:28 ` Daniel P. Berrangé
  2020-09-15 15:36 ` Philippe Mathieu-Daudé
  2020-09-23 12:42 ` Stefan Hajnoczi
  2 siblings, 0 replies; 4+ messages in thread
From: Daniel P. Berrangé @ 2020-09-15 15:28 UTC (permalink / raw)
  To: Stefan Hajnoczi; +Cc: libvir-list, Peter Maydell, philmd, qemu-devel

On Tue, Sep 15, 2020 at 04:07:34PM +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.
> 
> 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é <berrange@redhat.com>
> Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
> ---
> v2:
>  * Use Dan's suggested wording [Daniel Berrange]
> ---
>  docs/system/deprecated.rst | 9 +++++----
>  1 file changed, 5 insertions(+), 4 deletions(-)

Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>


Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|



^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [PATCH v2] docs/system: clarify deprecation schedule
  2020-09-15 15:07 [PATCH v2] docs/system: clarify deprecation schedule Stefan Hajnoczi
  2020-09-15 15:28 ` Daniel P. Berrangé
@ 2020-09-15 15:36 ` Philippe Mathieu-Daudé
  2020-09-23 12:42 ` Stefan Hajnoczi
  2 siblings, 0 replies; 4+ messages in thread
From: Philippe Mathieu-Daudé @ 2020-09-15 15:36 UTC (permalink / raw)
  To: Stefan Hajnoczi, qemu-devel; +Cc: libvir-list, Peter Maydell, Daniel Berrange

On 9/15/20 5:07 PM, 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.
> 
> 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é <berrange@redhat.com>
> Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>

Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>

> ---
> 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
>  
>  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.
>  
>  Prior to the 2.10.0 release there was no official policy on how
>  long features would be deprecated prior to their removal, nor
> 



^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [PATCH v2] docs/system: clarify deprecation schedule
  2020-09-15 15:07 [PATCH v2] docs/system: clarify deprecation schedule Stefan Hajnoczi
  2020-09-15 15:28 ` Daniel P. Berrangé
  2020-09-15 15:36 ` Philippe Mathieu-Daudé
@ 2020-09-23 12:42 ` Stefan Hajnoczi
  2 siblings, 0 replies; 4+ messages in thread
From: Stefan Hajnoczi @ 2020-09-23 12:42 UTC (permalink / raw)
  To: qemu-devel; +Cc: libvir-list, Peter Maydell, philmd, Daniel Berrange

[-- Attachment #1: Type: text/plain, Size: 960 bytes --]

On Tue, Sep 15, 2020 at 04:07:34PM +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.
> 
> 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é <berrange@redhat.com>
> Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
> ---
> v2:
>  * Use Dan's suggested wording [Daniel Berrange]
> ---
>  docs/system/deprecated.rst | 9 +++++----
>  1 file changed, 5 insertions(+), 4 deletions(-)

Thanks, applied to my block tree:
https://github.com/stefanha/qemu/commits/block

Stefan

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2020-09-23 12:46 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-09-15 15:07 [PATCH v2] docs/system: clarify deprecation schedule Stefan Hajnoczi
2020-09-15 15:28 ` Daniel P. Berrangé
2020-09-15 15:36 ` Philippe Mathieu-Daudé
2020-09-23 12:42 ` Stefan Hajnoczi

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.