<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 09.07.2012 19:27, Jeff Grossman
wrote:<br>
</div>
<blockquote
cite="mid:CACFCYpFTF5x5+2vtxbw9dnsntEGGe6MB=ho4eR9jY8GtyQ9nCg@mail.gmail.com"
type="cite">
<meta http-equiv="Context-Type" content="text/html;
charset=ISO-8859-1">
On Mon, Jul 9, 2012 at 9:57 AM, Kai Engert <span><<a
moz-do-not-send="true" href="mailto:kaie@kuix.de">kaie@kuix.de</a>></span>
wrote: <br>
<div>
<div><br>
</div>
<div>I think the plan is to base the Gecko version on the ESR
version of Thunderbird. That means they will not be changing
the Gecko version unless they release a new ESR, which if I am
not mistaken only happens about once a year. While the
Firefox developers might change Gecko and harm Thunderbird,
that should be caught in comm-central which has roughly a year
to fix until the next ESR release. I am sure that if
comm-central breaks, somebody will probably fix it rather
quickly.</div>
</div>
</blockquote>
<br>
Not every kind of breakage can automatically be detected by
automated tests. There are areas where nobody had had the
time/resources to write automated tests yet. Especially error
reporting is a difficult area, because you need deliberately
broken/misbehaving servers in order to test the correct application
behaviour.<br>
<br>
Kai<br>
<br>
</body>
</html>