qemu-trivial
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH] qemu-deprecated: Remove text about Python 2


From: John Snow
Subject: Re: [PATCH] qemu-deprecated: Remove text about Python 2
Date: Mon, 16 Mar 2020 14:16:43 -0400
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.4.1


On 1/30/20 5:09 PM, Philippe Mathieu-Daudé wrote:
> On 1/15/20 6:16 PM, John Snow wrote:
>> On 1/15/20 11:04 AM, Markus Armbruster wrote:
>>> Daniel P. Berrangé <address@hidden> 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.
> 
> In case you forgot :P
> 

Working on it.

Here's the list:

3.1.0:

b24ec3c46281286a6a5624d0ceb5fa6f30bd8a4f
7f8fc971558219891ced425e8fe7a65d2a8f131f
572023f7b235679716c4e57c9d701d83444f14b8
36699ab480340b928f2e589d83a94e6786e1965b
ec86faa934cb31d97f738134547137f16d17c0d0
a69dc537cc1a6d3c3cb35d30197ed45914a150c3
1d9cb42c5654772efec1977957584a21763013a1
2feac451d2b4492aa8a67f40bd20dd351941d1a2
fdaf2d5885209634bf9d9f643cec5323efb4525c
d18572dd9a4ee3f66d205912edae4d87a58ec11f
89d85cde75143325205e332dd97bf1bb8402d7c1

4.0.0:

93aee84f575d46699f49af3c96194012527e0b22
cc425b5ddfe8f8474814f369409e637c36898542
5a0e75f0a9ad063ebaa7eb19b82104f00acb80a0
0015ca5cbabe0b31d31610ddfaafd90a9e5911a4
4882206430532af27aa2ffd30df2818e4661e981
09bd7ba9f5f7bd1c0cf62ba89731ae3cc6d1c72e
292fa230cb9ef7d2ca2a1db59f0ff843e538f075
9fd7e96aab30d219bceb67f768fed01bedf1199f
b5ec7de7b5111f898453f96bdfd095fc1d8f6e18
e6e40f80cdf37021deb8c4f4311724a64461a1d1

5.0.0:

b3e2bb9458af556cb8aa0558f59222f462b81069
1d4ffe8dc77cbc9aafe8bcf514ca0e43f85aaae3
30d2a17b46e9b2979e91f6d85c8b0da98879a879
b2ce76a0730e48e60633a698cd876d55917ac9bc
a1e8bd2f5c2a7b42b243c9422f3a86e530665e9f
68a86dc15ccdf0f1242dc71b3d8da18a3ee6b8be


Just need to turn into patches.

--js




reply via email to

[Prev in Thread] Current Thread [Next in Thread]