intrigeri:
> Hi,
>
> Georg Koppen:
>> intrigeri:
>>> This relaxes me a bit regarding #27466, #26553, and #28044
>>> (Tor bugs, not Tails tickets).
>
>> No worries about those. We think we don't get those bugs into a stable
>> release shape for 8.5. They will be 9.0 material if at all.
>
> OK, so in the end it looks like 8.5 should not bring big changes for
> us (at least not those we had on our radar already as potential deal
> breakers).
One big thing we'll get into 8.5 and that is still missing in the
current alphas is the redesign of our security controls, see: #25658 for
details. Not sure how this affects Tails, though.
>>> Does this mean that the first 8.5.x release that has *no*
>>> corresponding 8.0.x will be the 2019-05-14 one?
>
>> I am not sure exactly what you mean but let me come up with my best
>> guess. :)
>
>> Assuming there are _no_ emergency releases in between, then the release
>> planned for 2019-05-14 will be the first stable release picking up
>> Firefox security bug fixes that will be based on 8.5 while the
>> corresponding alpha will be 9.0aX.
>
> What I need to understand is essentially: what's our deadline to make
> sure Tails is ready to ship Tor Browser 8.5.
>
> I think I now understood that:
>
> * If there's an emergency release, late March or in April, then it
> may be based on 8.5 (depending on how ready the 8.5 tree is).
>
> * Else, if there's no emergency release between the time the 8.5 tree
> is ready to be called stable, and May 14, then the first Tor
> Browser 8.5 release Tails needs to ship will be the May 14 one.
>
> It follows that Tails needs to be ready before late March to upgrade
> to 8.5, in case there's an emergency release.
I think that's correct.
Georg
