QEMU-Devel Archive on lore.kernel.org
 help / color / Atom feed
* [PATCH] qemu-deprecated: Remove text about Python 2
@ 2020-01-09  9:51 Thomas Huth
  2020-01-09 12:49 ` Aleksandar Markovic
  2020-01-13 22:36 ` John Snow
  0 siblings, 2 replies; 8+ messages in thread
From: Thomas Huth @ 2020-01-09  9:51 UTC (permalink / raw)
  To: Eduardo Habkost, qemu-devel; +Cc: qemu-trivial

Python 2 support has been removed, so we should now also remove
the announcement text for the deprecation.

Signed-off-by: Thomas Huth <thuth@redhat.com>
---
 qemu-deprecated.texi | 8 --------
 1 file changed, 8 deletions(-)

diff --git a/qemu-deprecated.texi b/qemu-deprecated.texi
index 7033e531de..8b23e98474 100644
--- a/qemu-deprecated.texi
+++ b/qemu-deprecated.texi
@@ -341,14 +341,6 @@ they have no effect when used with @option{-n} to skip image creation.
 Silently ignored options can be confusing, so this combination of
 options will be made an error in future versions.
 
-@section Build system
-
-@subsection Python 2 support (since 4.1.0)
-
-In the future, QEMU will require Python 3 to be available at
-build time.  Support for Python 2 in scripts shipped with QEMU
-is deprecated.
-
 @section Backwards compatibility
 
 @subsection Runnability guarantee of CPU models (since 4.1.0)
-- 
2.18.1



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

* Re: [PATCH] qemu-deprecated: Remove text about Python 2
  2020-01-09  9:51 [PATCH] qemu-deprecated: Remove text about Python 2 Thomas Huth
@ 2020-01-09 12:49 ` Aleksandar Markovic
  2020-01-13 22:36 ` John Snow
  1 sibling, 0 replies; 8+ messages in thread
From: Aleksandar Markovic @ 2020-01-09 12:49 UTC (permalink / raw)
  To: Thomas Huth; +Cc: qemu-trivial, Eduardo Habkost, qemu-devel

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

On Thursday, January 9, 2020, Thomas Huth <thuth@redhat.com> wrote:

> Python 2 support has been removed, so we should now also remove
> the announcement text for the deprecation.
>
> Signed-off-by: Thomas Huth <thuth@redhat.com>
> ---
>  qemu-deprecated.texi | 8 --------
>  1 file changed, 8 deletions(-)
>
>
Reviewed by: Aleksandar Markovic <amarkovic@wavecomp.com>


> diff --git a/qemu-deprecated.texi b/qemu-deprecated.texi
> index 7033e531de..8b23e98474 100644
> --- a/qemu-deprecated.texi
> +++ b/qemu-deprecated.texi
> @@ -341,14 +341,6 @@ they have no effect when used with @option{-n} to
> skip image creation.
>  Silently ignored options can be confusing, so this combination of
>  options will be made an error in future versions.
>
> -@section Build system
> -
> -@subsection Python 2 support (since 4.1.0)
> -
> -In the future, QEMU will require Python 3 to be available at
> -build time.  Support for Python 2 in scripts shipped with QEMU
> -is deprecated.
> -
>  @section Backwards compatibility
>
>  @subsection Runnability guarantee of CPU models (since 4.1.0)
> --
> 2.18.1
>
>
>

[-- Attachment #2: Type: text/html, Size: 1865 bytes --]

<br><br>On Thursday, January 9, 2020, Thomas Huth &lt;<a href="mailto:thuth@redhat.com">thuth@redhat.com</a>&gt; wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Python 2 support has been removed, so we should now also remove<br>
the announcement text for the deprecation.<br>
<br>
Signed-off-by: Thomas Huth &lt;<a href="mailto:thuth@redhat.com">thuth@redhat.com</a>&gt;<br>
---<br>
 qemu-deprecated.texi | 8 --------<br>
 1 file changed, 8 deletions(-)<br>
<br></blockquote><div><br></div><div><span style="color:rgb(34,34,34);font-size:14px;line-height:22.1200008392334px">Reviewed by: Aleksandar Markovic &lt;</span><a href="mailto:amarkovic@wavecomp.com" target="_blank" style="font-size:14px;line-height:22.1200008392334px">amarkovic@wavecomp.com</a><span style="color:rgb(34,34,34);font-size:14px;line-height:22.1200008392334px">&gt;</span><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
diff --git a/qemu-deprecated.texi b/qemu-deprecated.texi<br>
index 7033e531de..8b23e98474 100644<br>
--- a/qemu-deprecated.texi<br>
+++ b/qemu-deprecated.texi<br>
@@ -341,14 +341,6 @@ they have no effect when used with @option{-n} to skip image creation.<br>
 Silently ignored options can be confusing, so this combination of<br>
 options will be made an error in future versions.<br>
<br>
-@section Build system<br>
-<br>
-@subsection Python 2 support (since 4.1.0)<br>
-<br>
-In the future, QEMU will require Python 3 to be available at<br>
-build time.  Support for Python 2 in scripts shipped with QEMU<br>
-is deprecated.<br>
-<br>
 @section Backwards compatibility<br>
<br>
 @subsection Runnability guarantee of CPU models (since 4.1.0)<br>
-- <br>
2.18.1<br>
<br>
<br>
</blockquote>

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

* Re: [PATCH] qemu-deprecated: Remove text about Python 2
  2020-01-09  9:51 [PATCH] qemu-deprecated: Remove text about Python 2 Thomas Huth
  2020-01-09 12:49 ` Aleksandar Markovic
@ 2020-01-13 22:36 ` John Snow
  2020-01-14 10:08   ` Thomas Huth
  1 sibling, 1 reply; 8+ messages in thread
From: John Snow @ 2020-01-13 22:36 UTC (permalink / raw)
  To: Thomas Huth, Eduardo Habkost, qemu-devel; +Cc: qemu-trivial



On 1/9/20 4:51 AM, Thomas Huth wrote:
> Python 2 support has been removed, so we should now also remove
> the announcement text for the deprecation.
> 
> Signed-off-by: Thomas Huth <thuth@redhat.com>

Reviewed-by: John Snow <jsnow@redhat.com>

> ---
>  qemu-deprecated.texi | 8 --------
>  1 file changed, 8 deletions(-)
> 
> diff --git a/qemu-deprecated.texi b/qemu-deprecated.texi
> index 7033e531de..8b23e98474 100644
> --- a/qemu-deprecated.texi
> +++ b/qemu-deprecated.texi
> @@ -341,14 +341,6 @@ they have no effect when used with @option{-n} to skip image creation.
>  Silently ignored options can be confusing, so this combination of
>  options will be made an error in future versions.
>  
> -@section Build system
> -
> -@subsection Python 2 support (since 4.1.0)
> -
> -In the future, QEMU will require Python 3 to be available at
> -build time.  Support for Python 2 in scripts shipped with QEMU
> -is deprecated.
> -
>  @section Backwards compatibility
>  
>  @subsection Runnability guarantee of CPU models (since 4.1.0)
> 

Genuine question, I'm sorry:

Is it worth documenting things we recently removed? Right now, we don't
really have these docs hosted in a searchable way online in a
per-version format. Once the notice is gone, it's gone from the mirror.

I removed some bitmap functionality not too long ago and I created a
"Recently Removed" section as a bit of a troubleshooting guide should it
be needed.

- Do we want this section?
- Should I remove it?
- Can we add historical docs to the website to see previous deprecated
docs in a searchable manner?

--js



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

* Re: [PATCH] qemu-deprecated: Remove text about Python 2
  2020-01-13 22:36 ` John Snow
@ 2020-01-14 10:08   ` Thomas Huth
  2020-01-14 10:20     ` Daniel P. Berrangé
  0 siblings, 1 reply; 8+ messages in thread
From: Thomas Huth @ 2020-01-14 10:08 UTC (permalink / raw)
  To: John Snow, Eduardo Habkost, qemu-devel; +Cc: qemu-trivial

On 13/01/2020 23.36, John Snow wrote:
> 
> 
> On 1/9/20 4:51 AM, Thomas Huth wrote:
>> Python 2 support has been removed, so we should now also remove
>> the announcement text for the deprecation.
>>
>> Signed-off-by: Thomas Huth <thuth@redhat.com>
> 
> Reviewed-by: John Snow <jsnow@redhat.com>
> 
>> ---
>>  qemu-deprecated.texi | 8 --------
>>  1 file changed, 8 deletions(-)
>>
>> diff --git a/qemu-deprecated.texi b/qemu-deprecated.texi
>> index 7033e531de..8b23e98474 100644
>> --- a/qemu-deprecated.texi
>> +++ b/qemu-deprecated.texi
>> @@ -341,14 +341,6 @@ they have no effect when used with @option{-n} to skip image creation.
>>  Silently ignored options can be confusing, so this combination of
>>  options will be made an error in future versions.
>>  
>> -@section Build system
>> -
>> -@subsection Python 2 support (since 4.1.0)
>> -
>> -In the future, QEMU will require Python 3 to be available at
>> -build time.  Support for Python 2 in scripts shipped with QEMU
>> -is deprecated.
>> -
>>  @section Backwards compatibility
>>  
>>  @subsection Runnability guarantee of CPU models (since 4.1.0)
>>
> 
> Genuine question, I'm sorry:
> 
> Is it worth documenting things we recently removed?

Basically yes. In case of Python 2, it's not a QEMU feature that we
remove here, but a build requirement, and we tell the users that we need
at least Python 3.5 when they run "configure", so I'm not sure whether
that needs to be explicitely mentioned again the docs beside our ChangeLog?

> Right now, we don't
> really have these docs hosted in a searchable way online in a
> per-version format. Once the notice is gone, it's gone from the mirror.
> 
> I removed some bitmap functionality not too long ago and I created a
> "Recently Removed" section as a bit of a troubleshooting guide should it
> be needed.
> 
> - Do we want this section?
> - Should I remove it?
> - Can we add historical docs to the website to see previous deprecated
> docs in a searchable manner?

I also once started a page in the Wiki here:

 https://wiki.qemu.org/Features/RemovedFeatures

... but apparently, it did not get enough attention yet, otherwise you
would have noticed it before introducing the new chapter into the
qemu-doc ...

We definitely need one spot where we can document removed features. I
don't mind which way we do it, either the qemu-doc or the wiki, but we
should unify on one of the two. I guess the qemu-doc is the better place
since we are tracking the deprecated features there already and one more
or less just has to move the text to the other chapter when things get
finally removed?

 Thomas



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

* Re: [PATCH] qemu-deprecated: Remove text about Python 2
  2020-01-14 10:08   ` Thomas Huth
@ 2020-01-14 10:20     ` Daniel P. Berrangé
  2020-01-14 15:53       ` John Snow
  2020-01-15 16:04       ` Markus Armbruster
  0 siblings, 2 replies; 8+ messages in thread
From: Daniel P. Berrangé @ 2020-01-14 10:20 UTC (permalink / raw)
  To: Thomas Huth; +Cc: qemu-trivial, John Snow, Eduardo Habkost, qemu-devel

On Tue, Jan 14, 2020 at 11:08:16AM +0100, Thomas Huth wrote:
> On 13/01/2020 23.36, John Snow wrote:
> > 
> > 
> > On 1/9/20 4:51 AM, Thomas Huth wrote:
> >> Python 2 support has been removed, so we should now also remove
> >> the announcement text for the deprecation.
> >>
> >> Signed-off-by: Thomas Huth <thuth@redhat.com>
> > 
> > Reviewed-by: John Snow <jsnow@redhat.com>
> > 
> >> ---
> >>  qemu-deprecated.texi | 8 --------
> >>  1 file changed, 8 deletions(-)
> >>
> >> diff --git a/qemu-deprecated.texi b/qemu-deprecated.texi
> >> index 7033e531de..8b23e98474 100644
> >> --- a/qemu-deprecated.texi
> >> +++ b/qemu-deprecated.texi
> >> @@ -341,14 +341,6 @@ they have no effect when used with @option{-n} to skip image creation.
> >>  Silently ignored options can be confusing, so this combination of
> >>  options will be made an error in future versions.
> >>  
> >> -@section Build system
> >> -
> >> -@subsection Python 2 support (since 4.1.0)
> >> -
> >> -In the future, QEMU will require Python 3 to be available at
> >> -build time.  Support for Python 2 in scripts shipped with QEMU
> >> -is deprecated.
> >> -
> >>  @section Backwards compatibility
> >>  
> >>  @subsection Runnability guarantee of CPU models (since 4.1.0)
> >>
> > 
> > Genuine question, I'm sorry:
> > 
> > Is it worth documenting things we recently removed?
> 
> Basically yes. In case of Python 2, it's not a QEMU feature that we
> remove here, but a build requirement, and we tell the users that we need
> at least Python 3.5 when they run "configure", so I'm not sure whether
> that needs to be explicitely mentioned again the docs beside our ChangeLog?

In general changed build pre-requisites such as new minimum software
versions are documented in the release notes:

   https://wiki.qemu.org/ChangeLog/5.0#Build_Information

We normally would not list build pre-requisites in the deprecation notes
at all, since they don't follow the deprecation process normally. We
just update minimum versions immediately that our supported OS build
platforms change due to an OS going end of life. So for example we
have in the past bumped gnutls, glib, nettle, gcc, etc min versions
with no warning.  So the fact that Python 2 was mentioned in the
deprecations at all was slightly unusual. This is mostly just to be
nice to users since the OS platforms here aren't going EOL and still
ship Python 2, we simply don't wish to support it any more, since
the distros also all have Py 3.


> 
> > Right now, we don't
> > really have these docs hosted in a searchable way online in a
> > per-version format. Once the notice is gone, it's gone from the mirror.
> > 
> > I removed some bitmap functionality not too long ago and I created a
> > "Recently Removed" section as a bit of a troubleshooting guide should it
> > be needed.
> > 
> > - Do we want this section?
> > - Should I remove it?
> > - Can we add historical docs to the website to see previous deprecated
> > docs in a searchable manner?
> 
> I also once started a page in the Wiki here:
> 
>  https://wiki.qemu.org/Features/RemovedFeatures
> 
> ... but apparently, it did not get enough attention yet, otherwise you
> would have noticed it before introducing the new chapter into the
> qemu-doc ...
> 
> We definitely need one spot where we can document removed features. I
> don't mind which way we do it, either the qemu-doc or the wiki, but we
> should unify on one of the two. I guess the qemu-doc is the better place
> since we are tracking the deprecated features there already and one more
> or less just has to move the text to the other chapter when things get
> finally removed?

Yeah, I've said in the past that we should not be deleting deprecations
from the docs entirely.

If you look at GTK docs for example, you'll see they keep a record of
all incompatible or noteworth changes between release:

  https://developer.gnome.org/gtk3/stable/gtk-migrating-3-x-to-y.html

IMHO, we should follow this and have an appendix of removed features,
with sub-sections per QEMU release listing each removed feature. Thus
deprecation docs just get moved to this appendix at the right time.

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] 8+ messages in thread

* Re: [PATCH] qemu-deprecated: Remove text about Python 2
  2020-01-14 10:20     ` Daniel P. Berrangé
@ 2020-01-14 15:53       ` John Snow
  2020-01-15 16:04       ` Markus Armbruster
  1 sibling, 0 replies; 8+ messages in thread
From: John Snow @ 2020-01-14 15:53 UTC (permalink / raw)
  To: Daniel P. Berrangé, Thomas Huth
  Cc: qemu-trivial, Eduardo Habkost, qemu-devel



On 1/14/20 5:20 AM, Daniel P. Berrangé wrote:
> On Tue, Jan 14, 2020 at 11:08:16AM +0100, Thomas Huth wrote:
>> On 13/01/2020 23.36, John Snow wrote:
>>>
>>>
>>> On 1/9/20 4:51 AM, Thomas Huth wrote:
>>>> Python 2 support has been removed, so we should now also remove
>>>> the announcement text for the deprecation.
>>>>
>>>> Signed-off-by: Thomas Huth <thuth@redhat.com>
>>>
>>> Reviewed-by: John Snow <jsnow@redhat.com>
>>>
>>>> ---
>>>>  qemu-deprecated.texi | 8 --------
>>>>  1 file changed, 8 deletions(-)
>>>>
>>>> diff --git a/qemu-deprecated.texi b/qemu-deprecated.texi
>>>> index 7033e531de..8b23e98474 100644
>>>> --- a/qemu-deprecated.texi
>>>> +++ b/qemu-deprecated.texi
>>>> @@ -341,14 +341,6 @@ they have no effect when used with @option{-n} to skip image creation.
>>>>  Silently ignored options can be confusing, so this combination of
>>>>  options will be made an error in future versions.
>>>>  
>>>> -@section Build system
>>>> -
>>>> -@subsection Python 2 support (since 4.1.0)
>>>> -
>>>> -In the future, QEMU will require Python 3 to be available at
>>>> -build time.  Support for Python 2 in scripts shipped with QEMU
>>>> -is deprecated.
>>>> -
>>>>  @section Backwards compatibility
>>>>  
>>>>  @subsection Runnability guarantee of CPU models (since 4.1.0)
>>>>
>>>
>>> Genuine question, I'm sorry:
>>>
>>> Is it worth documenting things we recently removed?
>>
>> Basically yes. In case of Python 2, it's not a QEMU feature that we
>> remove here, but a build requirement, and we tell the users that we need
>> at least Python 3.5 when they run "configure", so I'm not sure whether
>> that needs to be explicitely mentioned again the docs beside our ChangeLog?
> 
> In general changed build pre-requisites such as new minimum software
> versions are documented in the release notes:
> 
>    https://wiki.qemu.org/ChangeLog/5.0#Build_Information
> 
> We normally would not list build pre-requisites in the deprecation notes
> at all, since they don't follow the deprecation process normally. We
> just update minimum versions immediately that our supported OS build
> platforms change due to an OS going end of life. So for example we
> have in the past bumped gnutls, glib, nettle, gcc, etc min versions
> with no warning.  So the fact that Python 2 was mentioned in the
> deprecations at all was slightly unusual. This is mostly just to be
> nice to users since the OS platforms here aren't going EOL and still
> ship Python 2, we simply don't wish to support it any more, since
> the distros also all have Py 3.
> 
> 
>>
>>> Right now, we don't
>>> really have these docs hosted in a searchable way online in a
>>> per-version format. Once the notice is gone, it's gone from the mirror.
>>>
>>> I removed some bitmap functionality not too long ago and I created a
>>> "Recently Removed" section as a bit of a troubleshooting guide should it
>>> be needed.
>>>
>>> - Do we want this section?
>>> - Should I remove it?
>>> - Can we add historical docs to the website to see previous deprecated
>>> docs in a searchable manner?
>>
>> I also once started a page in the Wiki here:
>>
>>  https://wiki.qemu.org/Features/RemovedFeatures
>>
>> ... but apparently, it did not get enough attention yet, otherwise you
>> would have noticed it before introducing the new chapter into the
>> qemu-doc ...
>>
>> We definitely need one spot where we can document removed features. I
>> don't mind which way we do it, either the qemu-doc or the wiki, but we
>> should unify on one of the two. I guess the qemu-doc is the better place
>> since we are tracking the deprecated features there already and one more
>> or less just has to move the text to the other chapter when things get
>> finally removed?
> 
> Yeah, I've said in the past that we should not be deleting deprecations
> from the docs entirely.
> 
> If you look at GTK docs for example, you'll see they keep a record of
> all incompatible or noteworth changes between release:
> 
>   https://developer.gnome.org/gtk3/stable/gtk-migrating-3-x-to-y.html
> 
> IMHO, we should follow this and have an appendix of removed features,
> with sub-sections per QEMU release listing each removed feature. Thus
> deprecation docs just get moved to this appendix at the right time.
> 
> Regards,
> Daniel
> 

Everything said makes sense to me. My review here stands, thanks! (Sorry
for the derail.)

--js



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

* Re: [PATCH] qemu-deprecated: Remove text about Python 2
  2020-01-14 10:20     ` Daniel P. Berrangé
  2020-01-14 15:53       ` John Snow
@ 2020-01-15 16:04       ` Markus Armbruster
  2020-01-15 17:16         ` John Snow
  1 sibling, 1 reply; 8+ messages in thread
From: Markus Armbruster @ 2020-01-15 16:04 UTC (permalink / raw)
  To: Daniel P. Berrangé
  Cc: qemu-trivial, Thomas Huth, John Snow, Eduardo Habkost, qemu-devel

Daniel P. Berrangé <berrange@redhat.com> writes:

> On Tue, Jan 14, 2020 at 11:08:16AM +0100, Thomas Huth wrote:
>> On 13/01/2020 23.36, John Snow wrote:
>> > Right now, we don't
>> > really have these docs hosted in a searchable way online in a
>> > per-version format. Once the notice is gone, it's gone from the mirror.
>> > 
>> > I removed some bitmap functionality not too long ago and I created a
>> > "Recently Removed" section as a bit of a troubleshooting guide should it
>> > be needed.
>> > 
>> > - Do we want this section?
>> > - Should I remove it?
>> > - Can we add historical docs to the website to see previous deprecated
>> > docs in a searchable manner?
>> 
>> I also once started a page in the Wiki here:
>> 
>>  https://wiki.qemu.org/Features/RemovedFeatures
>> 
>> ... but apparently, it did not get enough attention yet, otherwise you
>> would have noticed it before introducing the new chapter into the
>> qemu-doc ...
>> 
>> We definitely need one spot where we can document removed features. I
>> don't mind which way we do it, either the qemu-doc or the wiki, but we
>> should unify on one of the two. I guess the qemu-doc is the better place
>> since we are tracking the deprecated features there already and one more
>> or less just has to move the text to the other chapter when things get
>> finally removed?
>
> Yeah, I've said in the past that we should not be deleting deprecations
> from the docs entirely.
>
> If you look at GTK docs for example, you'll see they keep a record of
> all incompatible or noteworth changes between release:
>
>   https://developer.gnome.org/gtk3/stable/gtk-migrating-3-x-to-y.html
>
> IMHO, we should follow this and have an appendix of removed features,
> with sub-sections per QEMU release listing each removed feature. Thus
> deprecation docs just get moved to this appendix at the right time.

This is exactly the "Recently Removed" appendix John added in commit
3264ffced3d.

Now we need a sucker^Wvolunteer to restore all the stuff we dropped from
appendix "Deprecated features" to this appendix.  John, you were
incautious enough to signal you care; what about you?



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

* Re: [PATCH] qemu-deprecated: Remove text about Python 2
  2020-01-15 16:04       ` Markus Armbruster
@ 2020-01-15 17:16         ` John Snow
  0 siblings, 0 replies; 8+ messages in thread
From: John Snow @ 2020-01-15 17:16 UTC (permalink / raw)
  To: Markus Armbruster, Daniel P. Berrangé
  Cc: qemu-trivial, Thomas Huth, Eduardo Habkost, qemu-devel



On 1/15/20 11:04 AM, Markus Armbruster wrote:
> Daniel P. Berrangé <berrange@redhat.com> writes:
> 
>> On Tue, Jan 14, 2020 at 11:08:16AM +0100, Thomas Huth wrote:
>>> On 13/01/2020 23.36, John Snow wrote:
>>>> Right now, we don't
>>>> really have these docs hosted in a searchable way online in a
>>>> per-version format. Once the notice is gone, it's gone from the mirror.
>>>>
>>>> I removed some bitmap functionality not too long ago and I created a
>>>> "Recently Removed" section as a bit of a troubleshooting guide should it
>>>> be needed.
>>>>
>>>> - Do we want this section?
>>>> - Should I remove it?
>>>> - Can we add historical docs to the website to see previous deprecated
>>>> docs in a searchable manner?
>>>
>>> I also once started a page in the Wiki here:
>>>
>>>  https://wiki.qemu.org/Features/RemovedFeatures
>>>
>>> ... but apparently, it did not get enough attention yet, otherwise you
>>> would have noticed it before introducing the new chapter into the
>>> qemu-doc ...
>>>
>>> We definitely need one spot where we can document removed features. I
>>> don't mind which way we do it, either the qemu-doc or the wiki, but we
>>> should unify on one of the two. I guess the qemu-doc is the better place
>>> since we are tracking the deprecated features there already and one more
>>> or less just has to move the text to the other chapter when things get
>>> finally removed?
>>
>> Yeah, I've said in the past that we should not be deleting deprecations
>> from the docs entirely.
>>
>> If you look at GTK docs for example, you'll see they keep a record of
>> all incompatible or noteworth changes between release:
>>
>>   https://developer.gnome.org/gtk3/stable/gtk-migrating-3-x-to-y.html
>>
>> IMHO, we should follow this and have an appendix of removed features,
>> with sub-sections per QEMU release listing each removed feature. Thus
>> deprecation docs just get moved to this appendix at the right time.
> 
> This is exactly the "Recently Removed" appendix John added in commit
> 3264ffced3d.
> 
> Now we need a sucker^Wvolunteer to restore all the stuff we dropped from
> appendix "Deprecated features" to this appendix.  John, you were
> incautious enough to signal you care; what about you?
> 

Can add to the pile, but admittedly I am a little backlogged trying to
recover from the holidays. I can't promise any time to it right this minute.

I can try next week, if I don't forget.



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

end of thread, back to index

Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-01-09  9:51 [PATCH] qemu-deprecated: Remove text about Python 2 Thomas Huth
2020-01-09 12:49 ` Aleksandar Markovic
2020-01-13 22:36 ` John Snow
2020-01-14 10:08   ` Thomas Huth
2020-01-14 10:20     ` Daniel P. Berrangé
2020-01-14 15:53       ` John Snow
2020-01-15 16:04       ` Markus Armbruster
2020-01-15 17:16         ` John Snow

QEMU-Devel Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/qemu-devel/0 qemu-devel/git/0.git
	git clone --mirror https://lore.kernel.org/qemu-devel/1 qemu-devel/git/1.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 qemu-devel qemu-devel/ https://lore.kernel.org/qemu-devel \
		qemu-devel@nongnu.org
	public-inbox-index qemu-devel

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.nongnu.qemu-devel


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git