From: George Dunlap <george.dunlap@eu.citrix.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Stefano Stabellini <stefano@stabellini.net>,
Ian Campbell <Ian.Campbell@citrix.com>,
Jan Beulich <JBeulich@suse.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: 4.3 Planning: Taking stock
Date: Wed, 23 Jan 2013 17:06:24 +0000 [thread overview]
Message-ID: <51001890.2020201@eu.citrix.com> (raw)
In-Reply-To: <20130123170519.GA22719@phenom.dumpdata.com>
On 23/01/13 17:05, Konrad Rzeszutek Wilk wrote:
> On Wed, Jan 23, 2013 at 04:32:05PM +0000, George Dunlap wrote:
>> We're 4 months into our estimated 9-months release schedule, and 2 months
>> away from the scheduled feature freeze. It seems like a good time to take
>> stock of where we are and make sure we're on track for the release.
>>
>> Below are the features on my list, sorted by how likely they are to be
>> completed. Overall, the set of {completed, on-track} features looks pretty
>> good.
>>
>> The first question to ask is this this:
>>
>> 1. Are there any features we absolutely need for 4.3 that are not on this
>> list?
> PVH .. at least the hypercall number/format needs to be set in stone.
PVH is right at the top of the "features on track" section. :-) The
purpose of this question is to ask everyone to think about anything
*else* we we really need, so we don't end up with a 6-month feature
freeze again.
I think everyone agrees that PVH is a blocker. At the moment it doesn't
look like it needs any intervention; there's no particular need to talk
about interventions until something comes up.
-George
next prev parent reply other threads:[~2013-01-23 17:06 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-23 16:32 4.3 Planning: Taking stock George Dunlap
2013-01-23 16:52 ` George Dunlap
2013-01-23 17:00 ` Jan Beulich
2013-01-23 17:10 ` George Dunlap
2013-01-24 8:32 ` Jan Beulich
2013-01-24 9:49 ` Ian Campbell
2013-01-24 10:03 ` Jan Beulich
2013-01-24 10:07 ` Ian Campbell
2013-01-24 10:43 ` Jan Beulich
2013-01-23 17:54 ` Konrad Rzeszutek Wilk
2013-01-24 8:33 ` Jan Beulich
2013-01-24 11:16 ` Daniel Kiper
2013-01-24 11:12 ` George Dunlap
2013-01-24 11:34 ` Daniel Kiper
2013-01-23 17:17 ` Thanos Makatos
2013-01-23 22:03 ` James Harper
2013-01-24 9:45 ` Ian Campbell
2013-01-24 11:48 ` James Harper
2013-01-24 12:57 ` Bastian Blank
2013-01-24 13:15 ` Ian Campbell
2013-01-23 17:05 ` Konrad Rzeszutek Wilk
2013-01-23 17:06 ` George Dunlap [this message]
2013-02-12 10:32 ` Jan Beulich
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=51001890.2020201@eu.citrix.com \
--to=george.dunlap@eu.citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=JBeulich@suse.com \
--cc=konrad.wilk@oracle.com \
--cc=stefano@stabellini.net \
--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.