Re: [Xen-devel] Xen 4.3 development update, 18 March

[George Dunlap <george.dunlap@xxxxxxxxxxxxx>]

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

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel