From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Stefano Stabellini <stefano@aporeto.com>
Cc: sstabellini@kernel.org, wei.liu2@citrix.com,
George.Dunlap@eu.citrix.com, andrew.cooper3@citrix.com,
ian.jackson@eu.citrix.com, tim@xen.org, jbeulich@suse.com,
xen-devel@lists.xenproject.org
Subject: Re: [RFC v2] Xen PV Drivers Lifecycle
Date: Wed, 4 Jan 2017 15:19:20 -0500 [thread overview]
Message-ID: <20170104201920.GJ30554@char.us.oracle.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1701030939350.17742@sstabellini-ThinkPad-X260>
On Wed, Jan 04, 2017 at 10:00:01AM -0800, Stefano Stabellini wrote:
> Hi all,
>
> as you know, we have an issue with the speed of review and acceptance of
> new PV drivers. In a discussion among committers, George wrote an email
> with a short proposal to clarify the development lifecycle of new PV
> drivers and the different expectations at each stage of the process. I
> took that email, polished it and turned it into markdown. Here it is.
>
> ---
> Acks:
> +1 from Wei Liu
+1.
Albeit I am concerned about the
..
> from one stage to the next within a reasonable time frame unless someone
.. of what 'reasonable time' is when somebody is on vacation
or sick.
Is it worth spelling that out?
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-01-04 20:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-04 18:00 [RFC v2] Xen PV Drivers Lifecycle Stefano Stabellini
2017-01-04 18:40 ` Ian Jackson
2017-01-04 19:41 ` Stefano Stabellini
2017-01-04 20:19 ` Konrad Rzeszutek Wilk [this message]
2017-01-04 20:38 ` Stefano Stabellini
2017-01-11 18:49 ` Stefano Stabellini
2017-01-11 20:02 ` Konrad Rzeszutek Wilk
2017-01-13 1:53 ` Stefano Stabellini
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=20170104201920.GJ30554@char.us.oracle.com \
--to=konrad.wilk@oracle.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=sstabellini@kernel.org \
--cc=stefano@aporeto.com \
--cc=tim@xen.org \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.org \
/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.