From mboxrd@z Thu Jan 1 00:00:00 1970 From: George Dunlap Subject: Re: Release, RC5, and branching Date: Fri, 21 Feb 2014 16:54:20 +0000 Message-ID: <530784BC.7060307@eu.citrix.com> References: <53075C9E.9070608@eu.citrix.com> <21255.31702.826721.362385@mariner.uk.xensource.com> <21255.32527.955457.20429@mariner.uk.xensource.com> <53078433.60202@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <53078433.60202@citrix.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Andrew Cooper , Ian Jackson Cc: Stefano Stabellini , Ian Campbell , Jan Beulich , "xen-devel@lists.xen.org" List-Id: xen-devel@lists.xenproject.org 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