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

[Lars Kurth <lars.kurth.xen@xxxxxxxxx>]

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/" class="">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.

> 

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

Regards

Lars

On 10 Nov 2015, at 18:11, Sarah Conway <sconway@xxxxxxxxxxxxxxxxxxx> wrote:

I would still suggest adding positives knowing that some will find their own negatives. 

Sarah 

On Tue, Nov 10, 2015 at 12:56 PM, Lars Kurth <lars.kurth.xen@xxxxxxxxx> wrote:

On 10 Nov 2015, at 16:11, Sarah Conway <sconway@xxxxxxxxxxxxxxxxxxx> wrote:

Hi,

I made a few small copy edits. I was not able to open any of the links or view the slides, so please double-check that. 

Odd, they all work for me

A few comments:

- I would delete this sentence:  Some might be wondering what took me so long to write the announcement email and this blog post. 

I will leave this up to Wei. It's his personal style. If this was picked up, it's a nice harmless trap quote they can focus on. 

- Do you see any negatives stemming from continue to make release cycles shorter and more predictable? If so, can we address them head on? Or alternatively, expand more on the benefits of shorter, more predictable release cycles, draw comparisons to other OS projects that are following this trend. 

No negatives. I am not sure whether it's worthwhile doing this, but Ubuntu and OpenStack run 6 months cycles

- I looked over the slides and it seems like you are a lot more strict on what can be added during the RC part of the cycle. Am I mistaken here or was there a reasoning behind it?

The reasoning was, that there was a lot of arguing over freeze exceptions. In particular, because some vendors promised customers features in 4.6 - not all of which made it. Part of the rationale for shorter cycles is that the customer impact of a missing a release will be less severe. 

- For those that are interested in joining, list the email, mailing list to use.

I added a link

Lars

On Tue, Nov 10, 2015 at 7:20 AM, Wei Liu <wei.liu2@xxxxxxxxxx> wrote:

Hi all

I wrote a blog post with the help from Lars about the upcoming 4.7
release. Let me know if you have any comments.

https://blog.xenproject.org/?p=11139&preview=true

Thanks
Wei.

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

--

Sarah Conway

Director of PR Services, Collaborative Projects 

The Linux Foundation
sconway@xxxxxxxxxxxxxxxxxxx

(978) 578-5300  Cell

Skype:  sarah.k.conway

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

--

Sarah Conway

Director of PR Services, Collaborative Projects 

The Linux Foundation
sconway@xxxxxxxxxxxxxxxxxxx

(978) 578-5300  Cell

Skype:  sarah.k.conway

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