From: George Dunlap <george.dunlap@eu.citrix.com>
To: Russell Pavlicek <russell.pavlicek@citrix.com>,
George Dunlap <George.Dunlap@citrix.com>,
Lars Kurth <lars.kurth@citrix.com>,
Roger Pau Monne <roger.pau@citrix.com>,
xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: Xen 4.4 development update: RC0 imminent
Date: Fri, 6 Dec 2013 12:14:29 +0000 [thread overview]
Message-ID: <52A1BFA5.6040009@eu.citrix.com> (raw)
In-Reply-To: <55E78A57290FB64FA0D3CF672F9F3DA20F8803@SJCPEX01CL03.citrite.net>
On 12/05/2013 08:06 PM, Russell Pavlicek wrote:
>> That wasn't a yes/no question; it is a, "which do you think is best" question:
>> * Announcing features for external projects (linux, libvirt) in the main Xen release. Advantage: Longer list of features, more concentrated coverage
>> * Announcing features for external projects when the external projects release. Advantage: More frequent coverage, may build good-will between projects to announce their releases
> My gut: do both. Make noise in the Xen release, then make more noise when the external project releases. Preface the second one with "as we previously indicated during the release of XXXX..."
I hadn't considered that, but I suppose yes, that's even better. :-)
-George
next prev parent reply other threads:[~2013-12-06 12:14 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-05 16:09 Xen 4.4 development update: RC0 imminent George Dunlap
2013-12-05 16:29 ` George Dunlap
2013-12-05 16:34 ` Wei Liu
2013-12-05 16:39 ` George Dunlap
2013-12-05 16:48 ` Wei Liu
2013-12-05 16:59 ` Ian Campbell
2013-12-05 17:06 ` Wei Liu
2013-12-05 17:16 ` Ian Campbell
2013-12-05 17:34 ` Wei Liu
2013-12-05 17:53 ` George Dunlap
2013-12-05 18:03 ` Wei Liu
2013-12-06 9:27 ` Ian Campbell
2013-12-06 10:51 ` Wei Liu
2013-12-05 16:39 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-12-05 16:41 ` George Dunlap
2013-12-05 16:42 ` Roger Pau Monné
2013-12-05 16:51 ` George Dunlap
2013-12-05 17:01 ` Lars Kurth
2013-12-05 17:04 ` George Dunlap
2013-12-05 20:06 ` Russell Pavlicek
2013-12-05 23:54 ` Sander Eikelenboom
2013-12-06 9:39 ` Lars Kurth
2013-12-06 12:14 ` George Dunlap [this message]
2013-12-05 16:59 ` David Vrabel
2013-12-05 17:05 ` George Dunlap
2013-12-05 17:40 ` Dario Faggioli
2013-12-05 17:07 ` George Dunlap
2013-12-05 17:01 ` Olaf Hering
2013-12-05 17:06 ` David Vrabel
2013-12-05 17:32 ` Dario Faggioli
2013-12-06 13:30 ` Fabio Fantoni
2013-12-05 16:34 ` Andrew Cooper
2013-12-06 9:07 ` Jan Beulich
2013-12-06 13:07 ` George Dunlap
2013-12-06 14:58 ` Jan Beulich
2013-12-05 16:54 ` George Dunlap
2013-12-16 10:50 ` Lars Kurth
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=52A1BFA5.6040009@eu.citrix.com \
--to=george.dunlap@eu.citrix.com \
--cc=George.Dunlap@citrix.com \
--cc=lars.kurth@citrix.com \
--cc=roger.pau@citrix.com \
--cc=russell.pavlicek@citrix.com \
--cc=xen-devel@lists.xenproject.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.