On 03/07/18 12:23, Lars Kurth wrote:
> Combined reply to Jan and Roger
> Lars
> 
> On 03/07/2018, 11:07, "Roger Pau Monne" <roger....@citrix.com> wrote:
> 
>     On Mon, Jul 02, 2018 at 06:03:39PM +0000, Lars Kurth wrote:
>     > We then had a discussion around why the positive benefits didn't 
> materialize:
>     > * Andrew and a few other believe that the model isn't broken, but that 
> the issue is with how we 
>     >   develop. In other words, moving to a 9 months model will *not* fix 
> the underlying issues, but 
>     >   merely provide an incentive not to fix them.
>     > * Issues highlighted were:
>     >   * 2-3 months stabilizing period is too long
>     
>     I think one of the goals with the 6 month release cycle was to shrink
>     the stabilizing period, but it didn't turn that way, and the
>     stabilizing period is quite similar with a 6 or a 9 month release
>     cycle.
> 
> Right: we need to establish what the reasons are:
> * One has to do with a race condition between security issues and the desire 
> to cut a release which has issues fixed in it. If I remember correctly, that 
> has in effect almost added a month to the last few releases (more to this 
> one). 

The only way to avoid that would be to not allow any security fixes to
be included in the release the last few weeks before the planned release
date. I don't think this is a good idea. I'd rather miss the planned
release date.

BTW: the problem wasn't waiting for the security patches, but some
fixes for those needed. And this is something you can never rule out.
And waiting for the fixes meant new security fixes being ready...

> * One seems to have to do with issues with OSSTEST

... which in turn led to more security fixes being available.

> * <Please add other reasons>

We didn't look at the sporadic failing tests thoroughly enough. The
hypercall buffer failure has been there for ages, a newer kernel just
made it more probable. This would have saved us some weeks.


Juergen

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

Reply via email to