From mboxrd@z Thu Jan 1 00:00:00 1970 From: George Dunlap Subject: Re: Xen 4.4 development update: RC0 imminent Date: Thu, 5 Dec 2013 17:04:35 +0000 Message-ID: <52A0B223.70406@eu.citrix.com> References: <52A0ACE1.5040404@citrix.com> <52A0AF20.2080306@eu.citrix.com> 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 1VocMY-0006C5-NC for xen-devel@lists.xenproject.org; Thu, 05 Dec 2013 17:05:18 +0000 In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Lars Kurth , George Dunlap , Roger Pau Monne , xen-devel Cc: Russell Pavlicek List-Id: xen-devel@lists.xenproject.org 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