Figure out the right version string for Thunderbird 2



Build Config
11 years ago
11 years ago


(Reporter: Scott MacGregor, Assigned: Scott MacGregor)


Bug Flags:
blocking-thunderbird2 +

Firefox Tracking Flags

(Not tracked)




11 years ago
On the release branch, we made the version string in version.txt be:

Firefox used a value of:

Our in product pages where put on assuming we were going to use the same version string as Firefox. 

As a result, in the RC builds the following pages are not loading correctly:

1) The start page:
Currently has a value of:
Website expects:

2) Release Notes:
Current value:
Website expects:

We should figure out if we want to add redirects to the website to point back to /2.0/ or use the same version string that Firefox did.
Flags: blocking-thunderbird2+

Comment 1

11 years ago
Following firefox seems reasonable to me.
OS: Windows XP → All
Hardware: PC → All

Comment 2

11 years ago
I think we should set up the redirects.

We could arguably follow firefox, but I think Firefox did the wrong thing in having version numbers that change length. If the version number is going to be, then logically the .0 release is, not 2.0.

I meant to bring this up before 2.0 shipped, but got distracted/forgot.

Fortunately, we can still do the right thing for Thunderbird.

mscott: we have the builds already, so I think we'll need redirects, unless you want to rebuild for this version thing.

Comment 3

11 years ago
I'll file a bug for this Paul to either use redirects or move the files to /


Comment 4

11 years ago
I filed a bug on the website, Bug 375579 for those following along.
OS: All → Windows XP
Hardware: All → PC
So, if Thunderbird will be going with "", is there anything left to discuss / do in this bug?
OS: Windows XP → All
Hardware: PC → All

Comment 6

11 years ago
Reed, if you are ok on the website side with this then I don't think there's anything left to discuss here. 
Last Resolved: 11 years ago
Resolution: --- → FIXED
Thunderbird can't have their first release be

I suppose not.
You need to log in before you can comment on or make changes to this bug.