Re: [Xen-devel] Xen 4.4 development update: RC0 imminent

[Lars Kurth <lars.kurth@xxxxxxxxxx>]

> 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 would definitely include features which impact/improve/... Xen in the 
information we give to the PR folks for the Xen 4.4 announcement, but be clear 
about this. The PR folks, then have all the information and can make the most 
of it.

If they are covered elsewhere again : that increases the impact

Lars

________________________________________
From: Russell Pavlicek
Sent: 05 December 2013 20:06
To: George Dunlap; Lars Kurth; George Dunlap; Roger Pau Monne; xen-devel
Subject: RE: Xen 4.4 development update: RC0 imminent

>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@xxxxxxxxxxxxx]
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

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel