<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<link href="chrome://translator/skin/floatingPanel.css"
type="text/css" rel="stylesheet">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 05/07/2013 02:58, Josiah Bruner
wrote:<br>
</div>
<blockquote cite="mid:51D62837.7040209@programmer.net" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
Well, I thought about this for a while, in fact, I even started
writing several paragraphs on why we shouldn't do what you
suggested. However, as I thought about it some more, I must agree
with your points. The ideal solution would be to keep our version
number based on Gecko, while actually releasing a new product
every 6 weeks. Of course, that simply won't happen because of lack
of resources and frankly, lack of product. There would be no real
point.<br>
<br>
Jumps from 17 to 24 to 31, etc, are very confusing for our users
and may cause them to lose faith in its' development. Even looking
at the Thunderbird page causes people to wonder. (Though the
version of Thunderbird proceeding 24 should have some large
changes, and I want to redo the site then, which will help).
Anyway, this kind of jumping is just not beneficial in any way, so
I agree that Thunderbird 20XY needs to be the future.<br>
</blockquote>
There is only one thing which is missing here - if we follow this
"Microsoft Model" of naming the product, we will need additional
information visible to distinguish the maintenance releases;
Following the example of Microsoft Visual Studio, this would be
something like Tb 2014 SP 1 (Service Pack 1); this could than easily
mapped back to our internal version numbers (23.0.1, 23.0.2 etc.).
Also this assumes there is always only one "major" release per year,
is this in sync with reality?<br>
<br>
<img src="cid:part1.07070005.02000406@gmail.com" alt=""><br>
<br>
Also, since a lot of extensions use version comparator in order to
be backwards compatible, so I assume everything will remain the same
"behind the scenes"; we would just need a new separate function in
nsIXULAppInfo to return the "user friendly" version number.
(Obviously version and appVersion must remain unchanged)<br>
<blockquote cite="mid:51D62837.7040209@programmer.net" type="cite">
<br>
Thunderbird 2014 makes the product seem more developed,
professional, and trust-worthy. Of course, anyone with counter
points should most definitely respond in objection. I, on the
other hand, second the motion for Thunderbird 2014. I assume
though that people from within Mozilla will really make the final
ruling on this.<br>
</blockquote>
<br>
By the way, from a extension perspective the proportional number of
users who use old (pre 17.0) versions is worrying; therefore I added
a button to one of my addons (smartTemplate4) which is only visible
for numbers < 17.0.6:<br>
<br>
<img src="cid:part2.06050808.04060104@gmail.com" alt=""><br>
<br>
It offers the following explanation<br>
<br>
<img src="cid:part3.03030900.03070700@gmail.com" alt=""><br>
<br>
and opens the about page on clicking Ok (goes straight to the update
routine on Thunderbird 3.x, as the Help Menu item "check for
updates..." did)<br>
<br>
I feel strongly is that addons developers should also drive the
update of their users by reminding them, as a lot of users are
motivated (to lag behind) by trying to keep their addons compatible.
<br>
<br>
thanks,<br>
Axel <br>
<br>
<div class="moz-signature">-- <br>
<style type="text/css">
.myName:hover { font-size:13pt; text-shadow: 3px 3px 4px rgba(200,250,200,0.7);}
.moz-signature {opacity: 1.0 !important;}
</style>
<div id="testSignature" style="width: 65%; padding: 0.8em 1.2em;
font:x-small verdana; color: #444; box-shadow: 4px 4px 9px -2px
rgba(0,0,0,0.65); border-radius: 1em; padding: 0.4em 2em;
border: 1px dashed #444; background: rgb(230,240,163);
background: linear-gradient(to bottom, rgba(230,240,163,1)
0%,rgba(210,230,56,1) 50%,rgba(195,216,37,1)
51%,rgba(219,240,67,1) 100%); background:
-moz-linear-gradient(top, rgba(230,240,163,1) 0%,
rgba(210,230,56,1) 50%, rgba(195,216,37,1) 51%,
rgba(219,240,67,1) 100%);">
<b class="myName" style="text-shadow: 1px 1px 2px
#DDD;cursor:pointer;-moz-transition-property:font-size;
-moz-transition-duration: 0.5s;">
Axel Grude</b>
<br>
Software Developer
<br>
Thunderbird Add-ons Developer
<span style="color:#666666; font-size:xx-small">(QuickFolders,
quickFilters, QuickPasswords, Zombie Keys, SmartTemplate4)</span>
<br>
AMO Editor </div>
</div>
</body>
</html>