From mboxrd@z Thu Jan  1 00:00:00 1970
From: George Dunlap <George.Dunlap@eu.citrix.com>
Subject: Re: Xen 4.4 development update: RC0 imminent
Date: Thu, 5 Dec 2013 16:54:10 +0000
Message-ID: <CAFLBxZaVKZ2WffX2Zf822qTXX_p15uqVFpD6g8N2JfhREkBCdg@mail.gmail.com>
References: <CAFLBxZYvTK9BiVwi=Nt48aSRAZ_1xFY5dHNdnMVzGMtF8JUFOg@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <dunlapg@gmail.com>) id 1VocBo-0004Yl-AK
	for xen-devel@lists.xenproject.org; Thu, 05 Dec 2013 16:54:12 +0000
Received: by mail-we0-f176.google.com with SMTP id w62so11005592wes.7
	for <xen-devel@lists.xenproject.org>;
	Thu, 05 Dec 2013 08:54:11 -0800 (PST)
In-Reply-To: <CAFLBxZYvTK9BiVwi=Nt48aSRAZ_1xFY5dHNdnMVzGMtF8JUFOg@mail.gmail.com>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: xen-devel <xen-devel@lists.xenproject.org>, Lars Kurth <lars.kurth@xen.org>, Russell Pavlicek <russell.pavlicek@citrix.com>
List-Id: xen-devel@lists.xenproject.org

On Thu, Dec 5, 2013 at 4:09 PM, George Dunlap
<George.Dunlap@eu.citrix.com> wrote:
> This information will be mirrored on the Xen 4.4 Roadmap wiki page:
>  http://wiki.xen.org/wiki/Xen_Roadmap/4.4
>
> We're nearly to the completion of the code freeze, scheduled for
> tomorrow.  After the code freeze, only bug fixes and features marked
> as "blockers" will be considered.  At the moment, the only feature
> considered a blocker is experimental PVH dom0 support.
>
> In early RCs, most bug fixes will be accepted; but in later RCs, even
> bug fixes may be rejected if they risk breaking more important
> functionality than they fix.
>
> I don't think at this point every bug fix needs a blessing from me;
> committers, if there are fixes which are obviously low-risk, just go
> ahead and check them in.
>
> I was thinking that for some of our new features, it would be good to
> have a blog post describing the feature and how to test it.  This
> would both raise awareness of the feature, and hopefully get it more
> testing before the release.  We could choose a couple to focus on for
> each test day.

Lars / Russ,

We should be able to cut an RC0 sometime next week.  Do you want to
plan a test day for 16 December, and then maybe another one for 6
January?

 -George