From: George Dunlap <george.dunlap@eu.citrix.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Xen 4.3 development update CODE FREEZE HAS_BEGUN
Date: Tue, 16 Apr 2013 13:39:17 +0100 [thread overview]
Message-ID: <516D4675.7070300@eu.citrix.com> (raw)
In-Reply-To: <1366115833.8399.183.camel@zakaz.uk.xensource.com>
On 16/04/13 13:37, Ian Campbell wrote:
> On Tue, 2013-04-16 at 13:22 +0100, 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
>>
>> At this point, code will begin freezing.
>>
>> This means that every patch will need an exception to be accepted. The
>> bar for acceptance will be relatively low this week, but will continue
>> to raise until the May 6th code freeze.
>>
>> The key goals we're focusing on now, in order, are as follows:
>> 1. Have a bug-free 4.3 release
>> 2. Have an awesome 4.3 release
>> 3. Have a 4.3 release that happens on schedule (ready by June 15th)
>>
>> So my goal right now is to ensure, to the best of my ability, that:
>> 1. No new bugs are introduced that will not be discovered before the
>> release
>> 2. If no code is added, then either:
> ^new?
Er, not sure how that got past the proofreading... yes, it should say:
2. If new code is added, then either:
- It does not cause the release to slip
- If it causes the release to slip, then it was worth the cost.
>> * Install into /usr/local by default
>> owner: Ian Campbell
Great, thanks.
-George
next prev parent reply other threads:[~2013-04-16 12:39 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-16 12:22 Xen 4.3 development update CODE FREEZE HAS_BEGUN George Dunlap
2013-04-16 12:37 ` Ian Campbell
2013-04-16 12:39 ` George Dunlap [this message]
2013-04-16 12:50 ` George Dunlap
2013-04-16 15:02 ` Wei Liu
2013-04-16 15:20 ` George Dunlap
2013-04-16 16:11 ` Wei Liu
2013-04-16 16:24 ` George Dunlap
2013-04-18 18:09 ` Wei Liu
2013-04-19 7:50 ` Ian Campbell
2013-04-19 18:22 ` Wei Liu
2013-04-16 12:51 ` George Dunlap
2013-04-16 12:57 ` Jan Beulich
2013-04-16 13:00 ` George Dunlap
2013-04-16 13:16 ` Jan Beulich
2013-04-16 15:16 ` George Dunlap
2013-04-16 15:34 ` Anthony PERARD
2013-04-18 11:30 ` Stefano Stabellini
2013-04-18 14:50 ` Roger Pau Monné
2013-04-18 16:26 ` George Dunlap
2013-04-18 19:58 ` Alex Bligh
2013-04-19 8:07 ` 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=516D4675.7070300@eu.citrix.com \
--to=george.dunlap@eu.citrix.com \
--cc=Ian.Campbell@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.