From mboxrd@z Thu Jan 1 00:00:00 1970 From: George Dunlap Subject: Re: Xen 4.4 development update: RC0 imminent Date: Fri, 6 Dec 2013 12:14:29 +0000 Message-ID: <52A1BFA5.6040009@eu.citrix.com> References: <52A0ACE1.5040404@citrix.com> <52A0AF20.2080306@eu.citrix.com> <52A0B223.70406@eu.citrix.com> <55E78A57290FB64FA0D3CF672F9F3DA20F8803@SJCPEX01CL03.citrite.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VouIt-0006Gq-JC for xen-devel@lists.xenproject.org; Fri, 06 Dec 2013 12:14:43 +0000 In-Reply-To: <55E78A57290FB64FA0D3CF672F9F3DA20F8803@SJCPEX01CL03.citrite.net> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Russell Pavlicek , George Dunlap , Lars Kurth , Roger Pau Monne , xen-devel List-Id: xen-devel@lists.xenproject.org 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