From: Keir Fraser <keir.xen@gmail.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: xen-devel <xen-devel@lists.xen.org>
Subject: Re: Time for 4.2.0 rc0?
Date: Mon, 30 Jul 2012 13:28:35 +0100 [thread overview]
Message-ID: <CC3C3C83.39F0D%keir.xen@gmail.com> (raw)
In-Reply-To: <1343636817.14184.8.camel@zakaz.uk.xensource.com>
On 30/07/2012 09:26, "Ian Campbell" <Ian.Campbell@citrix.com> wrote:
> On Fri, 2012-07-27 at 11:54 +0100, Ian Campbell wrote:
>>> Yes, if the toolstack stuff is sorted sufficiently, we should definitely get
>>> on with the next step in the process!
>>
>> We should give the test system a chance to push (Ian J just added the
>> leak exception) and do it early next week sometime.
>
> We've now had a successful push.
>
> There are some fixes pending, but nothing mega-critical so I think we
> should go ahead with rc1.
>
> The release plan suggests weekly release candidates, does that work for
> you? If the overhead is burdensome we could go fortnightly.
The actual steps to create an RC are pretty trivial. Do you want me to tag
and sign an rc1 now? Is the qemu repo tagged with xen-4.2.0-rc1 yet?
-- Keir
> Ian.
>
next prev parent reply other threads:[~2012-07-30 12:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-27 10:09 Time for 4.2.0 rc0? Ian Campbell
2012-07-27 10:34 ` Keir Fraser
2012-07-27 10:54 ` Ian Campbell
2012-07-30 8:26 ` Ian Campbell
2012-07-30 12:28 ` Keir Fraser [this message]
2012-07-30 12:37 ` Ian Campbell
2012-07-30 12:41 ` Keir Fraser
2012-07-30 14:28 ` Ian Jackson
2012-07-30 14:42 ` Ian Jackson
2012-07-30 14:52 ` Ian Campbell
2012-07-30 14:56 ` Ian Jackson
2012-07-30 15:02 ` Ian Campbell
2012-07-30 15:05 ` Keir Fraser
2012-07-30 15:09 ` Ian Jackson
2012-07-30 15:12 ` Ian Campbell
2012-07-30 15:17 ` Keir Fraser
2012-07-30 15:20 ` Jan Beulich
2012-07-30 15:27 ` Ian Campbell
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=CC3C3C83.39F0D%keir.xen@gmail.com \
--to=keir.xen@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).