<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
I'm not sure I like it. A few main things:<br>
<ul>
<li>Changing artwork has the potential to cause brand confusion.
What's the official logo(s) etc? As Martin also said, you then
have to deal with trademarks for all the different logos you
come up with.</li>
<li>As others had said, you'll get the "which release is latest"
confusion in amongst users (who won't necessarily know/realising
that you're doing alphabetic, which is probably also mainly an
English-centric thing).</li>
<li>A text-string is just a version number but lacking
information. Some news vendors will likely add the number
anyway.</li>
<li>more below...<br>
</li>
</ul>
<br>
<div class="moz-cite-prefix">On 28/03/2015 23:44, R Kent James
wrote:<br>
</div>
<blockquote cite="mid:55173CD3.8060801@caspia.com" type="cite">
<meta http-equiv="content-type" content="text/html;
charset=windows-1252">
2) I want to counter the market sense that "Thunderbird is dead"
with a new message that we are alive and have an active community
moving forward. The <a moz-do-not-send="true"
href="https://blog.mozilla.org/thunderbird/2015/02/thunderbird-usage-continues-to-grow/">last
blog post</a> was a first step, and generated a lot of
discussion on the internet. A named release helps with that
message, "38" does not.<br>
</blockquote>
Releasing "Thunderbird Avocet" or "Thunderbird 38" don't actually do
anything to help counter "Thunderbird is dead" IMO - all it means is
that the releases have continued. What does help is "Thunderbird now
does <fancy new feature>" or "Thunderbird fixes big folders to
work smoothly and efficiently" or other similar headlines.<br>
<br>
A new release is just that - it happens regularly, probably fixes
some bugs. A new feature, or focussed bug fixing, is what really
counts towards making headlines.<br>
<br>
<br>
I think Firefox, Chrome and others have been trying to get away from
version numbers - or anything that represents version - as they've
realised the important bit for users is what's been improved. If you
look at the top few new reports for Chrome, none of the top ones
mention versions, for example "Google Adds Two New Features To
Chrome To Improve Page Load Times". You do seem to get version
numbers against the beta/early versions, but I think with today's
tech press that is inevitable (and we're never going to change tech
press and the technical folks wanting to know the numbers).<br>
<br>
I don't think we're going to get rid of version numbers whatever we
do. The important bit is what comes with each release, and to stress
that, rather than just "here's a new version".<br>
<br>
Mark<br>
<br>
<br>
</body>
</html>