From: Dario Faggioli <dario.faggioli@citrix.com>
To: George Dunlap <george.dunlap@eu.citrix.com>
Cc: Ian Campbell <ian.campbell@citrix.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
Jan Beulich <JBeulich@suse.com>
Subject: Re: Release, RC5, and branching
Date: Fri, 21 Feb 2014 18:11:35 +0100 [thread overview]
Message-ID: <1393002695.32038.831.camel@Solace> (raw)
In-Reply-To: <530784BC.7060307@eu.citrix.com>
[-- Attachment #1.1: Type: text/plain, Size: 967 bytes --]
On ven, 2014-02-21 at 16:54 +0000, George Dunlap wrote:
> On 02/21/2014 04:52 PM, Andrew Cooper wrote:
> > 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.
>
On one hand, that makes a lot of sense. On the other hand, perhaps,
having debug=y makes it easier to look at bugs reported by people
actually testing the RCs?
Perhaps, for next time of course, switch to debug=n when we feel like
we're ~ in the middle of the RC process?
just my 2 cents,
Dario
--
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2014-02-21 17:11 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
2014-02-21 17:05 ` Jan Beulich
2014-02-21 17:11 ` Dario Faggioli [this message]
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=1393002695.32038.831.camel@Solace \
--to=dario.faggioli@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=george.dunlap@eu.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.