From: Wei Liu <Wei.Liu2@citrix.com>
To: George Dunlap <George.Dunlap@eu.citrix.com>
Cc: Matthew Fioravante <matthew.fioravante@jhuapl.edu>,
wei.liu2@citrix.com, Ian Campbell <Ian.Campbell@citrix.com>,
Wei Liu <liuw@liuw.name>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
Jim Fehlig <jfehlig@suse.com>, Jan Beulich <JBeulich@suse.com>,
Anthony Perard <anthony.perard@citrix.com>,
Daniel De Graaf <dgdegra@tycho.nsa.gov>,
Roger Pau Monne <roger.pau@citrix.com>
Subject: Re: Xen 4.3 development update, and stock-taking
Date: Wed, 16 Jan 2013 18:15:03 +0000 [thread overview]
Message-ID: <1358360103.4842.15.camel@iceland> (raw)
In-Reply-To: <CAFLBxZZrWH9mT88tPsvBe1C7cJYA8UBBr1XxXUt4S26Df=bzzg@mail.gmail.com>
On Wed, 2013-01-16 at 17:55 +0000, George Dunlap wrote:
> Below is a summary of the projects / features being worked on for the
> 4.3 time frame. The tentative feature freeze is scheduled for 25
> March, which is just over 2 months away. With that in mind, I think
> it's time to take stock of the development, so we know whether to ask
> for more help or divert resources.
>
> To that end, I've added a line called "prognosis", indicating the
> likelihood of completion in the 4.3 timeframe. For items involving
> code hosted on the Xen.org site (including qemu-xen), that means a
> likelihood of having the feature code-complete and mostly working by
> the feature freeze. (It's OK if there are still bugs to be worked
> out.) For items in Linux, I think it would mean having items on track
> to make it into the kernel released just after the scheduled 4.3 time
> frame. Not sure what that means for libvirt. :-)
>
>
> I've given ratings to projects that I thought I had some insight on,
> but I would appreciate if everyone could review these and let me know
> if they're not accurate.
>
>
> I'd particularly appreciate it if the people listed below could give
> prognoses on the project listed.
>
> Meanings of prognoses:
> - Excellent: It would be very unlikely for this not to be finished in
> time.
> - Good: Everything is on track, and is likely to make it.
> - Fair: A pretty good chance of making it, but not as certain
> - Poor: Likely not to make it unless intervention is made
>
> - Not for 4.3: self-explanatory
>
>
>
> Mukesh Rathor: PVH
>
>
> Wei: Event channel scalability
>
>
I think I will rate my project as Good. Will send another RFC seires
(hopefully two) by the end of this month. But this is my first time to
estimate a real world project though.
Wei.
next prev parent reply other threads:[~2013-01-16 18:15 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-16 17:55 Xen 4.3 development update, and stock-taking George Dunlap
2013-01-16 18:03 ` Matthew Fioravante
2013-01-18 15:19 ` Konrad Rzeszutek Wilk
2013-01-18 21:17 ` Fioravante, Matthew E.
2013-01-16 18:15 ` Wei Liu [this message]
2013-01-17 10:50 ` George Dunlap
2013-01-17 9:09 ` Jan Beulich
2013-01-17 11:12 ` George Dunlap
2013-01-17 12:51 ` Jan Beulich
2013-01-17 13:58 ` George Dunlap
2013-01-17 14:15 ` Jan Beulich
2013-01-17 14:32 ` George Dunlap
2013-01-17 15:26 ` Jan Beulich
2013-01-17 15:30 ` Jan Beulich
2013-01-17 15:48 ` George Dunlap
2013-01-17 16:04 ` George Dunlap
2013-01-17 16:20 ` Jan Beulich
2013-01-17 17:22 ` George Dunlap
2013-01-17 16:14 ` Jan Beulich
2013-01-17 16:29 ` George Dunlap
2013-01-17 16:49 ` Jan Beulich
2013-01-17 17:11 ` George Dunlap
2013-01-18 9:35 ` Jan Beulich
2013-01-17 16:43 ` George Dunlap
2013-01-17 17:06 ` Jan Beulich
2013-01-17 16:49 ` George Dunlap
2013-01-18 9:30 ` Jan Beulich
2013-01-18 15:24 ` Konrad Rzeszutek Wilk
2013-01-18 11:20 ` Daniel Kiper
2013-01-21 14:12 ` George Dunlap
2013-01-22 13:53 ` Daniel Kiper
2013-01-22 14:10 ` Jan Beulich
2013-01-18 15:22 ` Konrad Rzeszutek Wilk
2013-01-17 10:00 ` Roger Pau Monné
2013-01-17 11:22 ` George Dunlap
2013-01-18 9:50 ` Roger Pau Monné
2013-01-18 15:21 ` Konrad Rzeszutek Wilk
2013-01-18 15:33 ` Roger Pau Monné
2013-01-21 15:06 ` George Dunlap
2013-01-17 10:20 ` Olaf Hering
2013-01-17 17:23 ` George Dunlap
2013-01-17 15:54 ` Daniel De Graaf
2013-01-17 15:49 ` George Dunlap
2013-01-18 15:41 ` Konrad Rzeszutek Wilk
2013-01-21 15:04 ` George Dunlap
2013-01-22 17:42 ` Konrad Rzeszutek Wilk
[not found] <mailman.21508.1358358967.1399.xen-devel@lists.xen.org>
2013-01-17 16:07 ` Andres Lagar-Cavilla
-- strict thread matches above, loose matches on Subject: below --
2013-01-22 14:32 Daniel Kiper
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=1358360103.4842.15.camel@iceland \
--to=wei.liu2@citrix.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=JBeulich@suse.com \
--cc=anthony.perard@citrix.com \
--cc=dgdegra@tycho.nsa.gov \
--cc=jfehlig@suse.com \
--cc=konrad.wilk@oracle.com \
--cc=liuw@liuw.name \
--cc=matthew.fioravante@jhuapl.edu \
--cc=roger.pau@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 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).