<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=windows-1252">
</head>
<body smarttemplateinserted="true" text="#000000" bgcolor="#FFFFFF">
<div id="smartTemplate4-template"><img style="margin-top: 1em;
float: right; box-shadow: 1px 1px 2px rgba(20, 20, 20, 0.4);"
moz-do-not-send="false" class="myLogo"
src="cid:part1.948A9104.B0BA3F06@gmail.com" alt="Get
Thunderbird!" height="15" width="94">
</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:
Thunderbird 60 beta - marketing the changes / improvements<br>
<b>From:</b>Tanstaafl <a class="moz-txt-link-rfc2396E" href="mailto:tanstaafl@libertytrek.org"><tanstaafl@libertytrek.org></a><br>
<b>To:</b>Tb-planning <br>
<b>Sent: </b>Monday, 26/03/2018 18:11:15 18:11 GMT ST +0100
[Week 13]<br>
</div>
</blockquote>
</div>
<blockquote type="cite"
cite="mid:4a50e248-0697-c262-bbb9-0c00c5ec5e59@libertytrek.org"
id="mid_4a50e248_0697_c262_bbb9_0c00c5ec5e59_libertytrek_org"
class=" cite">
<pre wrap="">I should have explicitly acknowledged the (obvious) fact that Patrick's
email was about 61, but how many times have things like this been
introduced in one version, only to be 'back-ported'?
Meaning, just because he first experienced it in a build of 61 doesn't
mean it won't be applied to the codebase for 60.
So, I still think the question needs to be addressed. Someone who has
access needs to ask Mozilla for an explicit answer to this question, so
that we KNOW what to expect - if for no other reason than to at least
know for certain that TB60 will be the last one that supports legacy Addons.
That would (or should) make a huge difference in the priorities of the
next TB Council (the elections for which are happening as we speak).</pre>
</blockquote>
<p>for me an official position on forking m-c would make the biggest
difference. Is it still a matter of <i>if</i> or is it just <i>when</i>?<br>
</p>
<p>IMHO We need to become independent to avoid arbitrary crippling
changes, and I would rather fork early than lose trust of my user
base. Forking will become necessary very soon, now that Mozilla is
hell bent on burning all bridges for XPCOM/XUL.<br>
</p>
<p>Of course I may be completely wrong and the changes are still
only minor but I see too many posts of the type "now that overlays
have gone away..." etc. on the firefox-dev groups that I know they
would love if we legacy developers would just go away silently
(well they kind of assume we have). As long as these questions
aren't answered I am still silently considering contingency
measures: how difficult it would be to create a Thunderbird Clone
(probably impossible), like Alex Kontos did with Waterfox.<br>
</p>
<p>Axel</p>
</body>
</html>