From: George Dunlap <george.dunlap@eu.citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
IanCampbell <ian.campbell@citrix.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: Release, RC5, and branching
Date: Fri, 21 Feb 2014 14:21:39 +0000 [thread overview]
Message-ID: <530760F3.9050000@eu.citrix.com> (raw)
In-Reply-To: <53076E4D020000780011E565@nat28.tlf.novell.com>
On 02/21/2014 02:18 PM, Jan Beulich wrote:
>>>> On 21.02.14 at 15:03, George Dunlap <george.dunlap@eu.citrix.com> wrote:
>> So it's now been several days, and no one has reported any major issues
>> with RC4. There are a handful of ARM-related fixes in the tree.
>>
>> I propose that we tag RC5 today, and make that the official release
>> (whenever we're ready to with the Linux Foundation PR process).
>>
>> 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.
>>
>> Thoughts?
> Fine with me, albeit it seems a bit pointless to me to have another
> RC, in particular if we expect this to become the release.
Isn't that what RC stands for -- release candidate? :-)
-George
next prev parent reply other threads:[~2014-02-21 14:21 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 [this message]
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
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=530760F3.9050000@eu.citrix.com \
--to=george.dunlap@eu.citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.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.