All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: russell.pavlicek@citrix.com, JBeulich@suse.com,
	ian.campbell@citrix.com, stefano.stabellini@citrix.com,
	ian.jackson@eu.citrix.com, xen-devel@lists.xenproject.org
Subject: Xen 4.5 RC2 (scheduled on the 12th). Committeers - please read.
Date: Mon, 10 Nov 2014 10:21:06 -0500	[thread overview]
Message-ID: <20141110152106.GL3783@laptop.dumpdata.com> (raw)

Hey,

The 'staging' has four extra patches:

e6fa63d pvgrub: ignore NUL
fda1614 xen/arm: Add support for GICv3 for domU
5a430ec tools: libxl: do not overrun input buffer in libxl__parse_mac
379b351 tools: libxl: do not leak diskpath during local disk attach

where the ' xen/arm: Add support for GICv3 for domU' is pretty significant
and I would like to have that in RC2.

As such, to give OSSTest breathing room to do its testing I would like
to ask committers to not checkin until the the 'e6fa63d' has cleared
and then we can tag RC2 right away (and perhaps it be done before Wednesday!)

Or if OSSTest has issues we have some time to figure it out.

The tentative dates are:

* Feature Freeze: 24th September 2014
* First RC: 24th October [Friday!]
 <==== <WE ARE HERE> =====>
* RC2: Nov 12th
* RC2 Test-day: Nov 13th
* RC3: Nov 24th
* RC3 Test-day: Nov 25th
* Release: 10th December 2014

Thank you.

             reply	other threads:[~2014-11-10 15:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-10 15:21 Konrad Rzeszutek Wilk [this message]
2014-11-11 16:38 ` Is: staging open for checkins. Was:Re: Xen 4.5 RC2 (scheduled on the 12th). Committeers - please read Konrad Rzeszutek Wilk

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=20141110152106.GL3783@laptop.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=JBeulich@suse.com \
    --cc=ian.campbell@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=russell.pavlicek@citrix.com \
    --cc=stefano.stabellini@citrix.com \
    --cc=xen-devel@lists.xenproject.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.