All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: Wei Liu <wei.liu2@citrix.com>
Cc: Jan Beulich <JBeulich@suse.com>, xen-devel <xen-devel@lists.xen.org>
Subject: Re: Xen 4.6 Development Update (two months reminder)
Date: Fri, 13 Mar 2015 10:32:41 +0000	[thread overview]
Message-ID: <1426242761.32572.109.camel@citrix.com> (raw)
In-Reply-To: <55018C770200007800068F44@mail.emea.novell.com>

(culling the cc list a lot)

On Thu, 2015-03-12 at 11:54 +0000, Jan Beulich wrote:
> >>> On 12.03.15 at 11:21, <wei.liu2@citrix.com> wrote:
> > == Linux ==
> 
> Wouldn't it make sense to move external projects down, and have
> our core pieces (hypervisor, tool stack, maybe qemu) be near the
> top?

When I originally started tracking external things back in whichever
release I was RM for there was only a couple of big ticket external
items. It seems that today there are dozens of things ranging from the
small to the large which are obscuring the work which is actually
happening within the Xen release itself (the list is now so long that is
a proper chore to read through it and pay attention).

Added to that is the fact that the list in general has become something
of a laundry list of everything anyone has ever thought of or someone
once considered working on, rather than things which are of some
importance to the 4.6 release.

Along with the fact that it must be a load of work to maintain I think
there is a danger nobody will read it because it is so overwhelming.

Wei, perhaps one or more of these could be applied:
      * raise the bar for inclusion in the list for external projects to
        be only the very largest most important items;
      * Stop tracking external projects altogether unless they have a
        direct interaction with the 4.6 release;
      * raise the bar for inclusion in the list for all projects a bit,
        i.e. not every little change to xen.git needs to be tracked;
      * be more aggressive about garbage collecting old ideas which
        aren't seeing any actual progress in this release window.

WRT the third one, I wonder if it is necessary for the RM to track
everything which is going on in the world WRT Xen. Just tracking those
items which we as a community have decided we want to get into 4.6 and
for which we feel there is a realistic chance of that happening would
make the list more manageable, which reduces the burden on you as well
as those trying to read the list.

I'm not saying that only things which are considered blockers for 4.6
should be on the list, but perhaps raise the bar from including every
possible wishlist item e.g. to only include important stuff, and drop
the nice to haves?

Ian.

  parent reply	other threads:[~2015-03-13 10:32 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-12 10:21 Xen 4.6 Development Update (two months reminder) wei.liu2
2015-03-12 10:54 ` George Dunlap
2015-03-12 11:26   ` Dario Faggioli
2015-03-12 11:34   ` Fabio Fantoni
2015-03-12 11:41     ` George Dunlap
2015-03-12 11:54 ` Jan Beulich
2015-03-12 14:15   ` Aravind Gopalakrishnan
2015-03-13 10:32   ` Ian Campbell [this message]
2015-03-16 10:43     ` Wei Liu
2015-03-16 15:58       ` Lars Kurth
2015-03-13 18:05   ` Konrad Rzeszutek Wilk
2015-03-12 12:18 ` Tamas Lengyel
2015-03-12 15:07 ` Ian Campbell
2015-03-12 15:39   ` Dario Faggioli
2015-03-12 15:57     ` Josh Whitehead
2015-03-12 19:25     ` Meng Xu
2015-03-12 16:01   ` Olaf Hering
2015-03-12 16:15     ` Dagaen Golomb
2015-03-12 18:31   ` Daniel Kiper
2015-03-13  8:40     ` Olaf Hering
2015-03-12 18:54 ` Aravindh Puthiyaparambil (aravindp)
2015-03-12 18:59 ` Daniel Kiper
2015-03-13  8:41   ` Olaf Hering
2015-03-13  3:02 ` Chun Yan Liu
2015-03-13  9:44 ` Chao Peng
2015-03-13 17:30 ` Ed White
2015-03-13 18:02 ` Konrad Rzeszutek Wilk
2015-03-13 18:05   ` Andrew Cooper
2015-03-13 18:12     ` Konrad Rzeszutek Wilk
2015-03-16 13:01 ` Mihai Donțu
2015-03-16 16:00   ` Lars Kurth
2015-03-16 16:18     ` Razvan Cojocaru
2015-03-16 16:51       ` Mihai Donțu

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=1426242761.32572.109.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xen.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.