Thunderbird versioning/Naming.

Axel Grude (Axel) axel.grude at
Fri Jul 5 19:33:25 UTC 2013

*To:* Axel Grude (Axel) <axel.grude at> - Axel [axel.grude at]
*From:* ace <acelists at> - ace acelists at <mailto:acelists at>
*CC:* tb-planning tb-planning at <mailto:tb-planning at>
*Sent: *Friday, 05/07/2013 15:48:58 15:48 GMT Standard Time {GMT ST} +0100 [Week 27]
*Subject:*Re: Thunderbird versioning/Naming.
> -------- Original Message --------
> Subject: Re: Thunderbird versioning/Naming.
> From: Axel Grude (Axel) <axel.grude at>
> To: tb-planning at
> Date: Fri, 05 Jul 2013 11:53:31 +0100
>> 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?
> No, the current release is 7cycles x 6weeks = 42 weeks which is shorter
> than a year. So either we extend the number of cycles or can do
> YEAR.MONTH version numbers.
hmm, I don't like fully coupling it to time variables (remember we still have a 6 
weeks cycle) - potentially you could have 2 security updates in short succession. And 
we shouldn't be tied to a fixed schedule (I thought this is exactly what this 
numbering gets us around).

So either Tb 2014.1  .. 2014.2 or better
Tb 2014
Tb 2014 SP1
Tb 2014 SP2
Tb 2014 SP3
Tb 2014 SP4

as the need arises.


*Axel <mailto:axel.grude at>*
Software Developer
Thunderbird Add-ons Developer (QuickFolders, quickFilters, QuickPasswords, Zombie 
Keys, SmartTemplate4)
AMO Editor
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the tb-planning mailing list