<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 7/5/2013 10:00 AM, Josiah Bruner
wrote:<br>
</div>
<blockquote cite="mid:51D6DFA3.9020904@programmer.net" type="cite">
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
Could you give some examples of the potential issues? Thanks!<br>
</blockquote>
<br>
Thunderbird version 3.0 is built on Gecko 1.9.1 and JavaScript
1.8.1, which powers Firefox 3.5 (except when it was 3.1) and
Seamonkey 2.0<br>
Firefox 4 (ex-3.7) uses Gecko 2.0 (ex-1.9.3) and JS 1.8.5 [no
corresponding TB release]<br>
Firefox/Thunderbird 1.5 is JS 1.6, Gecko 1.8.0, while Gecko 1.8 is
JS 1.7 and Firefox/Thunderbird 2.0.<br>
<br>
I, for one, like sanity in versioning. As a developer, it means I
can read "new in XXX 23" and know instantly where it applies,
instead of having to track down a convoluted correlation chart.<br>
<br>
Keeping the same version internally solves edge cases for issues
like aurora/beta build versions, and I would in no way countenance a
proposal to give the UI a different version number from the internal
guts. For end users, the version numbers they care about are
"up-to-date" and "not up-to-date." Let's not make it more
complicated.<br>
<pre class="moz-signature" cols="72">--
Joshua Cranmer
Thunderbird and DXR developer
Source code archæologist</pre>
</body>
</html>