Ben Hutchings:
> On Tue, 2016-02-02 at 07:34 +0000, Niels Thykier wrote:
> [...]
>>
>> Would you prefer that we moved future freezes (i.e. Buster and later),
>> so we could always rely on Greg's branch?
> 
> Yes, I would.
> 

Ok, we will take it into consideration for the planning of the next freeze.

> [...]
>>    - How certain are we on the 22nd being the actual release date?
> 
> I thought that 10 week cycles were rare, but I checked this and now I'm
> much less confident.  Rounding to the nearest week, the distribution of
> release cycle lengths from 3.2 to 4.4 inclusive, is:
> 
>  8 weeks: *           ( 1)
>  9 weeks: **********  (10)
> 10 weeks: **********  (10)
> 11 weeks: **          ( 2)
> 
> (I chose this range to exclude the 3.1 release delayed by the
> kernel.org compromise.)
> 
> So it seems quite possible that 4.10 could be released later in January
> or in February.
> 
> [...]

Ok, so a reasonable guess would be actually be 10 weeks, which puts us
at the 29th of January?  An upstream stable update would come 3-4 weeks
later.

>>  * How difficult/disruptive do you expect the migration to linux 4.10
>>    will be?
>>    - Is this something we can reasonably do within a month?  2 months?
> 
> Migration from what, 4.9?
> 

Yes - on the assumption that we are going to use 4.10, I presume it
would be easiest to upgrade from 4.9 rather than 4.4 (admittedly, I am
ignoring roll-backs for a moment).

>> [...]
> 
>>    - How long does Greg's LTS last?  We would spend at least a year of
>>      it before January 22nd 2017.
> 
> About 15 months.
> 
> [...]

So Greg's LTS will almost be over by the time 4.10 is released? Seems
like we are not getting a lot from sticking with 4.4 then?



From what I can gather so far:

 * We are looking at moving the freeze at least 2 months if we want
   Linux 4.10.
   - At +2 months, Linux 4.10 would be just before the "deep freeze"
     (Assuming a 10 week release cycle for Linux).

 * If we stick with 4.4, the Debian Linux maintainers receives
   practically no advantage from Greg's LTS effort.


Thanks,
~Niels



Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to