From: Paolo Bonzini <pbonzini@redhat.com>
To: Thomas Huth <thuth@redhat.com>, qemu-devel@nongnu.org
Cc: Daniel Berrange <berrange@redhat.com>, Jeff Cody <jcody@redhat.com>
Subject: Re: [Qemu-devel] [qemu-web PATCH v2] Add a blog post about deprecation of old interfaces and features
Date: Thu, 10 Aug 2017 11:15:37 +0200 [thread overview]
Message-ID: <edcf593a-52c8-bd43-e25d-520e628cedf4@redhat.com> (raw)
In-Reply-To: <1502354790-16927-1-git-send-email-thuth@redhat.com>
On 10/08/2017 10:46, Thomas Huth wrote:
> Now that we've got a list of deprecated interfaces/features in the QEMU
> documentation, it is time to draw some more public attention to our plans
> of removing certain interfaces/features in future releases.
>
> Signed-off-by: Thomas Huth <thuth@redhat.com>
> ---
> v2: Use a link to the qemu-doc instead of pointing to the Wiki
>
> _posts/2017-08-10-deprecation.md | 26 ++++++++++++++++++++++++++
> 1 file changed, 26 insertions(+)
> create mode 100644 _posts/2017-08-10-deprecation.md
>
> diff --git a/_posts/2017-08-10-deprecation.md b/_posts/2017-08-10-deprecation.md
> new file mode 100644
> index 0000000..784fb79
> --- /dev/null
> +++ b/_posts/2017-08-10-deprecation.md
> @@ -0,0 +1,26 @@
> +---
> +layout: post
> +title: "Deprecation of old parameters and features"
> +date: 2017-08-10 10:45:00 +0200
> +author: Thomas Huth
> +categories: [features, 'web site']
> +---
> +QEMU has a lot of interfaces (like command line options or HMP commands) and
> +old features (like certain devices) which are considered as deprecated
> +since other more generic or better interfaces/features have been established
> +instead. While the QEMU developers are generally trying to keep each QEMU
> +release compatible with the previous ones, the old legacy sometimes gets into
> +the way when developing new code and/or causes quite some burden of maintaining
> +it.
> +
> +Thus we are currently considering to get rid of some of the old interfaces
> +and features in a future release and have started to collect a list of such
> +old items in our
> +[QEMU documentation](https://qemu.weilnetz.de/doc/qemu-doc.html#Deprecated-features).
> +If you are running QEMU directly, please have a look at this deprecation
> +chapter of the QEMU documentation to see whether you are still using one of
> +these old interfaces or features, so you can adapt your setup to use the new
> +interfaces/features instead. Or if you rather think that one of the items
> +should *not* be removed from QEMU at all, please speak up on the
> +[qemu-devel mailing list](http://wiki.qemu.org/Contribute/MailingLists)
> +to explain why the interface or feature is still required.
>
Pushed, thanks.
Paolo
next prev parent reply other threads:[~2017-08-10 9:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-10 8:46 [Qemu-devel] [qemu-web PATCH v2] Add a blog post about deprecation of old interfaces and features Thomas Huth
2017-08-10 9:15 ` Paolo Bonzini [this message]
2017-08-10 9:23 ` Daniel P. Berrange
2017-08-10 9:24 ` Paolo Bonzini
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=edcf593a-52c8-bd43-e25d-520e628cedf4@redhat.com \
--to=pbonzini@redhat.com \
--cc=berrange@redhat.com \
--cc=jcody@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).