Re: [Publicity] Blog post: Xen Project 4.7 Planning Opens

[Wei Liu <wei.liu2@xxxxxxxxxx>]

On Wed, Nov 11, 2015 at 10:30:39AM +0000, Lars Kurth wrote:
> So how about:
> 
> > With Xen 4.6 released in October, we are already one month into the new 
> > cycle.
> Add...
> Which means it is time to start planning for the next release.
> 
> > Some might be wondering what took me so long to write the announcement 
> > email and this blog post. The reason is that Xen community underwent 
> > thorough
> > </a href="..." >discussion</a> on how to manage releases from xen-unstable 
> > and its impact on <a href="...">stable releases</a>. 
> Note (we always have waited for a month to start a new cycle, so no need to 
> apologise).
> 
> Instead, how about...
> You may remember that one of the goals of the <a 
> href="https://blog.xenproject.org/2015/02/16/xen-project-4-6-planning-opens/ 
> <https://blog.xenproject.org/2015/02/16/xen-project-4-6-planning-opens/>">4.6 
> release planning</a> was <em>to create smoother developer experience and to 
> release Xen 4.6 on time</em>. Both goals were achieved, so it was time to 
> think where to go from here. Thus, the Xen community underwent thorough
> > </a href="..." >discussion</a> on how to manage releases from xen-unstable 
> > and its impact on <a href="...">stable releases</a>. 
> Maybe replace: "manage releases" ... "manage future releases"
> 
> > After the 4.7 release, we will start to <strong>release Xen every 6 
> > months</strong>: at the beginning of <strong>June</strong> and 
> > <strong>December</strong>.
> Add ...
> A regular 6 monthly release schedule has worked well for Ubuntu, OpenStack 
> and many other projects. The idea behind it is a simple one: set a hard date 
> and modify your goals to match that timeline. Which is also, why we dropped 
> feature freeze exceptions, which create overheads and introduce unnecessary 
> risk and debate. In addition, the new fixed release schedule will help open 
> source projects and commercial vendors who consume Xen Project releases to 
> plan their own releases better. And it allows us to set a schedule that 
> ensures that every single release cycle is only affected by a single holiday 
> period and that we have a Xen Project developer event (be at a Hackathon or 
> Xen Project Developer Summit) during each release cycle.
> 

Fine by me.

> > 
> Replace with: "The stable release scheme is unchanged:18 months full support, 
> plus 18 months security fixes afterwards."
> After that leave things as they are


One negative point other might pick is that they say more release means
less resource for stable release maintenance. Not sure we need to
emphasise more on the unchanged stable release scheme.

-- 
Wei.

_______________________________________________
Publicity mailing list
Publicity@xxxxxxxxxxxxxxxxxxxx
http://lists.xenproject.org/cgi-bin/mailman/listinfo/publicity