From: "Daniel P. Berrange" <berrange@redhat.com>
To: qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>,
Stefan Hajnoczi <stefanha@redhat.com>,
"Daniel P. Berrange" <berrange@redhat.com>
Subject: [Qemu-devel] [PATCH v2 0/2] Document deprecated features & support lifecycle
Date: Tue, 6 Jun 2017 12:05:54 +0100 [thread overview]
Message-ID: <20170606110556.12922-1-berrange@redhat.com> (raw)
This is a followup to
v1: https://lists.gnu.org/archive/html/qemu-devel/2017-05/msg02390.html
The goal is to clarify to users & app developers what they can expect
from QEMU in terms of feature lifecycle & any deprecation policy should
it be neccessary to remove features.
Changed in v2:
- Split into 2 patches so we can consider each suggested addition
independantly.
Daniel P. Berrange (2):
docs: document deprecated features in appendix
docs: document support lifetime for features
qemu-doc.texi | 48 ++++++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 48 insertions(+)
--
2.9.3
next reply other threads:[~2017-06-06 11:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-06 11:05 Daniel P. Berrange [this message]
2017-06-06 11:05 ` [Qemu-devel] [PATCH v2 1/2] docs: document deprecated features in appendix Daniel P. Berrange
2017-06-23 11:44 ` Markus Armbruster
2017-06-23 11:49 ` Daniel P. Berrange
2017-06-06 11:05 ` [Qemu-devel] [PATCH v2 2/2] docs: document support lifetime for features Daniel P. Berrange
2017-06-23 11:48 ` Markus Armbruster
2017-06-23 11:54 ` Daniel P. Berrange
2017-06-23 12:19 ` Peter Maydell
2017-06-06 14:04 ` [Qemu-devel] [PATCH v2 0/2] Document deprecated features & support lifecycle Stefan Hajnoczi
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=20170606110556.12922-1-berrange@redhat.com \
--to=berrange@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@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 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.