<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">On 2020-02-04 15:52, Axel Grude wrote:<br>
</div>
<blockquote type="cite"
cite="mid:0ef07267-8ab9-66f3-caa2-2bca889b5b90@gmail.com">
<p>June! That's very early! - that doesn't feel like the <b>ESR
support period</b> 2019/2020 is even <b>close to a year</b>?
I know 68 was shipped "late" but feel it gave our (Add-on) users
a much needed "breathing period".<br>
</p>
</blockquote>
<p>The ESR time span is the same it always was. <br>
</p>
<blockquote type="cite"
cite="mid:0ef07267-8ab9-66f3-caa2-2bca889b5b90@gmail.com">
<p>I am very doubtful there will be anywhere close to enough APIs
available then for what we are doing, so we will have to ask our
users to "stay back" - and no doubt loose some Customers. I was
hoping for an automatic push in October at the earliest; can you
elaborate on the practical side how the automatic transition
into the new ESR period is planned?</p>
</blockquote>
<p>The last point release of the 68 series will roll out around
2020-08-25 and 68 End of Life is 2020-09-22, so that's the latest
we'd be holding off on upgrading 68 users to 78.</p>
<blockquote type="cite"
cite="mid:0ef07267-8ab9-66f3-caa2-2bca889b5b90@gmail.com">
<p>As the <b>minimum effort</b>, provided we rewrite all XUL code
and remove overlays, can we still use XPCOM in experiments with
78? </p>
</blockquote>
<p>Like Paul wrote, yes, experiments can basically do anything.</p>
<p> -Magnus<br>
</p>
</body>
</html>