From: Eric Blake <eblake@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>,
"Aleksandar Markovic" <aleksandar.m.mail@gmail.com>
Cc: "Thomas Huth" <thuth@redhat.com>,
"libvir-list@redhat.com" <libvir-list@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"Hervé Poussineau" <hpoussin@reactos.org>,
"Aleksandar Markovic" <amarkovic@wavecomp.com>,
"Aleksandar Rikalo" <aleksandar.rikalo@rt-rk.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Aurelien Jarno" <aurelien@aurel32.net>
Subject: Re: [libvirt] [PATCH-for-4.2] hw/mips: Deprecate the r4k machine
Date: Mon, 25 Nov 2019 09:48:30 -0600 [thread overview]
Message-ID: <cddf6ffc-9753-7a69-e02d-4c192dd78343@redhat.com> (raw)
In-Reply-To: <20191125154021.GI4157473@redhat.com>
On 11/25/19 9:40 AM, Daniel P. Berrangé wrote:
>> Please don't start any deprecation process. This requires certain
>> consultation within my company. Rest assured that everyone's opinion will
>> be taken into account while doing consiltation.
>
> The idea of having a deprecation process is precisely to
> allow time for people like to provide feedback before any
> deletion takes place. So this is not a reason to delay
> starting of deprecation.
>
> The process lasts for 2 releases before we delete anything:
>
> https://qemu.weilnetz.de/doc/qemu-doc.html#Deprecated-features
>
> When we start the clock now, it is deprecated when 5.0 releases
> in April 2020, and still deprecated with 5.1 in August 2020.
>
> The code won't be deleted until Sep 2020 when 5.2 dev cycle opens,
> and there's still time to undelete it right up until the 5.2 feature
> freeze in late Oct 2020. That's 11 months away, which is plenty of
> time for feedback IMHO.
And that's the soonest it could be removed. If your consultation reports
back that it is still needed, we can reverse the decision to deprecate
or extend the deprecation to last longer, as needed, rather than blindly
removing at the first possible moment.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
next prev parent reply other threads:[~2019-11-25 15:56 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-25 10:41 [PATCH-for-4.2] hw/mips: Deprecate the r4k machine Philippe Mathieu-Daudé
2019-11-25 14:45 ` Aleksandar Markovic
2019-11-25 14:56 ` Philippe Mathieu-Daudé
2019-11-25 15:40 ` [libvirt] " Daniel P. Berrangé
2019-11-25 15:48 ` Eric Blake [this message]
2019-11-27 19:40 ` Aleksandar Markovic
2019-11-27 21:12 ` Philippe Mathieu-Daudé
2019-11-25 15:23 ` Aurelien Jarno
2019-11-26 20:46 ` Aleksandar Markovic
2019-11-26 21:15 ` Philippe Mathieu-Daudé
2019-11-26 22:03 ` Aleksandar Markovic
2019-11-26 22:11 ` Philippe Mathieu-Daudé
2019-11-27 18:46 ` Aleksandar Markovic
2019-11-27 18:47 ` Aleksandar Markovic
2019-11-27 21:17 ` Philippe Mathieu-Daudé
2019-11-27 21:30 ` Aleksandar Markovic
2019-11-27 21:31 ` Aleksandar Markovic
2019-11-27 22:35 ` Philippe Mathieu-Daudé
2019-12-17 18:10 ` Thomas Huth
2019-12-17 18:43 ` [EXTERNAL]Re: " Aleksandar Markovic
2020-09-04 16:57 ` Philippe Mathieu-Daudé
2020-09-10 7:36 ` Philippe Mathieu-Daudé
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=cddf6ffc-9753-7a69-e02d-4c192dd78343@redhat.com \
--to=eblake@redhat.com \
--cc=aleksandar.m.mail@gmail.com \
--cc=aleksandar.rikalo@rt-rk.com \
--cc=amarkovic@wavecomp.com \
--cc=aurelien@aurel32.net \
--cc=berrange@redhat.com \
--cc=hpoussin@reactos.org \
--cc=libvir-list@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@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).