From mboxrd@z Thu Jan 1 00:00:00 1970 From: Russell Pavlicek Subject: Re: Xen 4.4 development update: RC0 imminent Date: Thu, 5 Dec 2013 20:06:16 +0000 Message-ID: <55E78A57290FB64FA0D3CF672F9F3DA20F8803@SJCPEX01CL03.citrite.net> References: <52A0ACE1.5040404@citrix.com> <52A0AF20.2080306@eu.citrix.com> <52A0B223.70406@eu.citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VofBl-0004bf-FC for xen-devel@lists.xenproject.org; Thu, 05 Dec 2013 20:06:21 +0000 In-Reply-To: <52A0B223.70406@eu.citrix.com> Content-Language: en-US List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: George Dunlap , Lars Kurth George Dunlap , Roger Pau Monne , xen-devel List-Id: xen-devel@lists.xenproject.org >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...". News is news until people know about it. We reach a very limited subset of the Open Source world with any piece of PR. Exercising an opportunity to announce & announce again (under the guise of a reminder to people) is prudent, IMO. We need to make lots of positive noise continually to overcome the existing market misconception that KVM is the future. It's kind of like the old adage of voting in Chicago: "Vote early; vote often." ;) Russ Pavlicek Xen Project Evangelist, Citrix Systems Home Office: +1-301-829-5327 Mobile: +1-240-397-0199 UK VoIP: +44 1223 852 894 -----Original Message----- From: George Dunlap [mailto:george.dunlap@eu.citrix.com] Sent: Thursday, December 05, 2013 12:05 PM To: Lars Kurth; George Dunlap; Roger Pau Monne; xen-devel Cc: Russell Pavlicek Subject: Re: Xen 4.4 development update: RC0 imminent On 12/05/2013 05:01 PM, Lars Kurth wrote: > >>> * Disk: indirect descriptors (in 3.11) >>> - ? >> It's part of the "Xen ecosystem", and so it should be tested and >> announced. It makes sense to me to announce developments that happen >> all together with Xen releases; we can make it clear that these are >> features in *external >> projects* that happened during the Xen 4.4 *timeframe*. The >> alternative would be to announce them when the other projects had a release; but I think that may be diluting the messaging a bit. >> >> In any case, if we don't announce them on Xen releases, we ought to pay attention and announce them when the projects do their release. >> >> Lars / Russ, any opinions here? > That works 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 -George