<html>
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
</head>
<body smarttemplateinserted="true">
<div id="smartTemplate4-template">
<style>.snipped {
border: 1px solid rgba(90,90,90,0.2); padding: 3px;
background: linear-gradient(to bottom, #fdeff4 0%,#fdb9bd 51%,#fea2a3 59%,#ff999e 100%);
}
#agGmail {
margin-left: 6px;
}
#agGmail, #agGmail p {
font-family: Cambria, Georgia, serif !important;
font-size:11pt;
text-align: left;
}
#agGmail p {
max-width: 950px;
}
</style>
<div id="agGmail"><br>
</div>
</div>
<div id="smartTemplate4-quoteHeader">
<style type="text/css" scoped="">
#newHeaderAG1 b { font-weight:bold; color: #990033; min-width: 4.5em; max-width:none; display:inline-block;}
</style>
<blockquote type="cite" style="margin-bottom: -20px !important;
padding-bottom:20px !important;">
<div id="newHeaderAG1" style="font-size: x-small; padding:1em;
background-color:rgba(220,220,240,0.4); border-radius:3px;"> <b>Subject:</b>Re:
Current timeline for de-supporting traditional add-ons<br>
<b>From:</b>Magnus Melin <a class="moz-txt-link-rfc2396E" href="mailto:mkmelin+mozilla@iki.fi"><mkmelin+mozilla@iki.fi></a><br>
<b>To:</b><a class="moz-txt-link-abbreviated" href="mailto:Tb-planning@mozilla.org">Tb-planning@mozilla.org</a>
<a class="moz-txt-link-rfc2396E" href="mailto:tb-planning@mozilla.org"><tb-planning@mozilla.org></a> <br>
<b>Sent: </b>Tuesday, 2/4/2020, 13:09 13:09 GMT +0000 [Week
6]<br>
</div>
</blockquote>
</div>
<blockquote type="cite"
cite="mid:eb90b05c-3cd7-0392-94b4-7066de74ec32@iki.fi">On
2020-02-03 22:48, Jon wrote:
<br>
<blockquote type="cite">Also, sorry to intrude but I'm following
along to better understand when
<br>
plugins used by human rights defenders (namely enigmail) will no
longer
<br>
work and in parallel how the integration of OpenPGP into
Thunderbird
<br>
directly is going (I am excited about this expanded, built in
capacity!).
<br>
</blockquote>
<br>
Enigmail will not work in Thunderbird 78, which for end users will
be released around 2020-06-30.
<br>
</blockquote>
<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>
<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>
<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? Completely removing XPCOM is my major pain point at this
stage. The official communications haven't been very clear on this
subject, they seem to push APIs that don't exist.</p>
<p>PS: "minimum effort" is still a major time investment for big
Add-ons. Most Add-on authors also have day jobs, I am going mine
part-time, but it is close to 30hours/week just doing development
/ marketing / support. So please do not assume we are just lazy.<br>
</p>
<p>regards,<br>
Axel<br>
</p>
</body>
</html>