From: George Dunlap <george.dunlap@eu.citrix.com>
To: Jan Beulich <JBeulich@suse.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 14:00:57 +0100 [thread overview]
Message-ID: <516D4B89.1050007@eu.citrix.com> (raw)
In-Reply-To: <516D66EE02000078000CD99F@nat28.tlf.novell.com>
On 16/04/13 13:57, Jan Beulich wrote:
>>>> On 16.04.13 at 14:22, George Dunlap <George.Dunlap@eu.citrix.com> 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.
> So how does this "accepting an exception" look from a formal POV?
> Do non-bug-fix patches need an additional ACK from you? Or are
> committers expected to use common sense? Or yet something else?
Well, I have not been elected to any position, nor am I the benevolent
dictator, so I am not in a position to dictate to committers what to
commit and what not to commit.
However, I would respectfully request that committers ask for an Ack
from me, if that is acceptable to everyone.
-George
next prev parent reply other threads:[~2013-04-16 13:00 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
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 [this message]
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=516D4B89.1050007@eu.citrix.com \
--to=george.dunlap@eu.citrix.com \
--cc=JBeulich@suse.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.