From: Rich Persaud <persaur@gmail.com>
To: Lars Kurth <lars.kurth@citrix.com>
Cc: "davorin.mista@aggios.com" <davorin.mista@aggios.com>,
Julien Grall <julien.grall@arm.com>,
"anastassios.nanos@onapp.com" <anastassios.nanos@onapp.com>,
"mirela.simonovic@aggios.com" <mirela.simonovic@aggios.com>,
"edgar.iglesias@xilinx.com" <edgar.iglesias@xilinx.com>,
"Ji, John" <john.ji@intel.com>,
"robin.randhawa@arm.com" <robin.randhawa@arm.com>,
"daniel.kiper@oracle.com" <daniel.kiper@oracle.com>,
Matt Spencer <Matt.Spencer@arm.com>,
xen-devel <xen-devel@lists.xenproject.org>,
Artem Mygaiev <Artem_Mygaiev@epam.com>,
Tamas K Lengyel <tamas.k.lengyel@gmail.com>,
Christopher Clark <christopher.w.clark@gmail.com>,
Paul Durrant <Paul.Durrant@citrix.com>,
"committers@xenproject.org" <committers@xenproject.org>,
"vfachin@de.adit-jv.com" <vfachin@de.adit-jv.com>,
"intel-xen@intel.com" <intel-xen@intel.com>,
Jarvis Roach <Jarvis.Roach@dornerworks.com>,
Juergen Gross <jgross@suse.com>,
Brian Woods <brian.woods@amd.com>,
"Natarajan, Janakarajan" <jnataraj@amd.com>,
Stefano Stabellini <sstabellini@kernel.org>,
Stewart Hildebrand <Stewart.Hildebrand@dornerworks.com>,
Volodymyr Babchuk <volodymyr_babchuk@epam.com>,
Roger Pau Monne <roger.pau@citrix.com>
Subject: Re: [Xen-devel] Xen Project Community Call June 27th (instead of July 4th): @15:00 UTC Call for agenda items
Date: Tue, 25 Jun 2019 15:38:21 -0400 [thread overview]
Message-ID: <FDD05784-1F9E-4654-8E79-3D432C571D4C@gmail.com> (raw)
In-Reply-To: <EDC3EB96-942F-484F-9EDB-F30E01151816@citrix.com>
> On Jun 25, 2019, at 12:36, Lars Kurth <lars.kurth@citrix.com> wrote:
>
> Hi all:
> please add your agenda items. I had only ONE series which was highlighted as needing attention from others. Is this seriously the only one?
Proposed agenda item: in the absence of Jira tickets, would it be useful to have a list (e.g. generated by a script) with the lifecycle status of all outstanding patch series, e.g.
METADATA
- bug fix / improvement / refactor / cleanup / new feature
- impacted Xen subsystems/components/features
- targeted version of Xen
- contributing person/org
- relevance of patch series to the goals set by RM for the next Xen release
- related patch series (with below status info)
STATUS:
- patch series version
- date of patch series v1
- no responses received + ping count + days since submission + days since ping
- reviewed with objections
- reviewed without objections, awaiting ack
- acked, awaiting merge
From such a summary, patch series could be prioritized for review/triage in the community call, based on uniform criteria and project-wide context.
Rich
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2019-06-25 19:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-21 15:45 [Xen-devel] Xen Project Community Call June 27th (instead of July 4th): @15:00 UTC Call for agenda items Lars Kurth
2019-06-25 16:36 ` Lars Kurth
2019-06-25 19:38 ` Rich Persaud [this message]
2019-06-25 20:17 ` Julien Grall
2019-06-25 20:27 ` Rich Persaud
2019-06-26 10:45 ` Lars Kurth
2019-06-26 15:43 ` Rich Persaud
2019-06-26 17:44 ` Stefano Stabellini
2019-06-26 19:15 ` Lars Kurth
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=FDD05784-1F9E-4654-8E79-3D432C571D4C@gmail.com \
--to=persaur@gmail.com \
--cc=Artem_Mygaiev@epam.com \
--cc=Jarvis.Roach@dornerworks.com \
--cc=Matt.Spencer@arm.com \
--cc=Paul.Durrant@citrix.com \
--cc=Stewart.Hildebrand@dornerworks.com \
--cc=anastassios.nanos@onapp.com \
--cc=brian.woods@amd.com \
--cc=christopher.w.clark@gmail.com \
--cc=committers@xenproject.org \
--cc=daniel.kiper@oracle.com \
--cc=davorin.mista@aggios.com \
--cc=edgar.iglesias@xilinx.com \
--cc=intel-xen@intel.com \
--cc=jgross@suse.com \
--cc=jnataraj@amd.com \
--cc=john.ji@intel.com \
--cc=julien.grall@arm.com \
--cc=lars.kurth@citrix.com \
--cc=mirela.simonovic@aggios.com \
--cc=robin.randhawa@arm.com \
--cc=roger.pau@citrix.com \
--cc=sstabellini@kernel.org \
--cc=tamas.k.lengyel@gmail.com \
--cc=vfachin@de.adit-jv.com \
--cc=volodymyr_babchuk@epam.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 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).