From: George Dunlap <george.dunlap@eu.citrix.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
Ian Campbell <ian.campbell@citrix.com>,
Jan Beulich <JBeulich@suse.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Release, RC5, and branching
Date: Fri, 21 Feb 2014 16:54:20 +0000 [thread overview]
Message-ID: <530784BC.7060307@eu.citrix.com> (raw)
In-Reply-To: <53078433.60202@citrix.com>
On 02/21/2014 04:52 PM, Andrew Cooper wrote:
> On 21/02/14 16:30, Ian Jackson wrote:
>> Ian Jackson writes ("Re: Release, RC5, and branching"):
>>> George Dunlap writes ("Release, RC5, and branching"):
>>>> After tagging RC5 this afternoon, I don't see much reason not to branch
>>>> -- I don't think at this point we're going to get much more testing in.
>>> OK. I'll do the branch after the RC5 tarball is made.
>> The RC5 tags and tarball are in the usual places. George, do you want
>> to send an RC announcement ?
>>
>> Ian.
> What about changing the build to not be debug by default, and the main
> Xen version? They will need to be done before the release.
Hmm, arguably that should be done once we start RCs, I would have
thought, so we're actually testing the codepaths we plan on releasing.
-George
next prev parent reply other threads:[~2014-02-21 16:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-21 14:03 Release, RC5, and branching George Dunlap
2014-02-21 14:18 ` Jan Beulich
2014-02-21 14:21 ` George Dunlap
2014-02-21 16:16 ` Ian Jackson
2014-02-21 16:30 ` Ian Jackson
2014-02-21 16:52 ` Andrew Cooper
2014-02-21 16:54 ` George Dunlap [this message]
2014-02-21 17:05 ` Jan Beulich
2014-02-21 17:11 ` Dario Faggioli
2014-02-21 16:34 ` George Dunlap
2014-02-21 16:49 ` Ian Jackson
2014-02-21 16:51 ` Ian Jackson
2014-02-21 17:04 ` Jan Beulich
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=530784BC.7060307@eu.citrix.com \
--to=george.dunlap@eu.citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=ian.campbell@citrix.com \
--cc=stefano.stabellini@eu.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 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.