From: George Dunlap <george.dunlap@eu.citrix.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Xen 4.3 development update, 18 March
Date: Tue, 19 Mar 2013 15:41:25 +0000 [thread overview]
Message-ID: <51488725.6080904@eu.citrix.com> (raw)
In-Reply-To: <20130318133914.GE24560@phenom.dumpdata.com>
On 03/18/2013 01:39 PM, Konrad Rzeszutek Wilk wrote:
> On Mon, Mar 18, 2013 at 12:13:40PM +0000, George Dunlap wrote:
>> This information will be mirrored on the Xen 4.3 Roadmap wiki page:
>> http://wiki.xen.org/wiki/Xen_Roadmap/4.3
>>
>> A couple of notes:
>>
>> - I have updated the timeline to include a description of my proposed
>> criteria for accepting patches going forward. Feedback is welcome.
>>
>> - As we focus on getting a release for the 4.3 codebase, I have
>> removed items from the list that are either "not for 4.3" or are
>> purely external (e.g., Linux kernel or libvirt).
>>
>> - Please start suggesting bug reports to put on this list.
>>
>> = Timeline =
>>
>> We are planning on a 9-month release cycle. Based on that, below are
>> our estimated dates:
>> * Feature freeze: 25 March 2013
>> * Code freezing point: 8 April 2013
>> * First RC: 6 May 2013
>> * Release: 17 June 2013
>>
>> The RCs and release will of course depend on stability and bugs, and
>> will therefore be fairly unpredictable. Each new feature will be
>> considered on a case-by-case basis; but the general rule will be as
>> follows:
>>
>> * Between feature freeze and code freeze, only features which have had
>> a v1 posted before the feature freeze, or are on this list, will be
>> considered for inclusion.
>
> Based on this, I think the PVH patches and the claim user-space patches,
> can be included past feature freeze right?
[snip]
> Mukesh just posted them last Friday (wohoo!). If we are to get it in
> this Friday (25 March), that is a tall order.
>
> Can we either slip the schedule or include it under the 'Code freezing
> point' - at which there is a bit more breathing room?
If you think slipping the schedule a few weeks will help us get PVH in
as a proper feature for 4.3, I'd be in favor of it. If it's a tech
preview, it depends on how much it affects other non-tech-preview code.
We'll have to take a closer look when we hit the code freeze.
-George
next prev parent reply other threads:[~2013-03-19 15:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-18 12:13 Xen 4.3 development update, 18 March George Dunlap
2013-03-18 12:27 ` Ian Campbell
2013-03-18 12:31 ` Stefano Stabellini
2013-03-18 13:47 ` Ian Campbell
2013-03-19 15:36 ` George Dunlap
2013-03-21 19:32 ` Stefano Stabellini
2013-03-18 13:11 ` Jan Beulich
2013-03-18 13:39 ` Konrad Rzeszutek Wilk
2013-03-19 15:41 ` George Dunlap [this message]
2013-03-19 13:24 ` Daniel Kiper
2013-03-19 15:48 ` George Dunlap
2013-03-19 15:53 ` George Dunlap
2013-03-20 10:57 ` James Harper
2013-03-19 16:00 ` Wei Liu
2013-03-20 1:33 ` Dario Faggioli
2013-03-21 9:19 ` Roger Pau Monné
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=51488725.6080904@eu.citrix.com \
--to=george.dunlap@eu.citrix.com \
--cc=konrad.wilk@oracle.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.