From mboxrd@z Thu Jan 1 00:00:00 1970 From: George Dunlap Subject: Re: Xen 4.3 development update CODE FREEZE HAS_BEGUN Date: Tue, 16 Apr 2013 14:00:57 +0100 Message-ID: <516D4B89.1050007@eu.citrix.com> References: <516D66EE02000078000CD99F@nat28.tlf.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <516D66EE02000078000CD99F@nat28.tlf.novell.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Jan Beulich Cc: "xen-devel@lists.xen.org" List-Id: xen-devel@lists.xenproject.org On 16/04/13 13:57, Jan Beulich wrote: >>>> On 16.04.13 at 14:22, 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. > 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