375579 - Version String issue for Thunderbird 2 in product pages

Status: RESOLVED FIXED

(www.mozilla.org :: General, defect)

Description

[Scott MacGregor]

Spun off from Bug 375555.

The Thunderbird 2 in product pages (the release notes and the start page) on mozilla.com assumed the version of the product was going to be 2.0 based on how Firefox 2 was released.

i.e.

http://en-US.www.mozilla.com/en-US/thunderbird/2.0/start/
and
http://en-us.www.mozilla.com/en-US/thunderbird/2.0/releasenotes/

In talking to the build team, we think the version string should be the actual version so: 2.0.0.0. Stealing a quote from preed:

 "but I think Firefox did the wrong thing in
having version numbers that change length. If the version number is going to be
2.0.0.1/2/3, then logically the .0 release is 2.0.0.0, 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."

Can we either:

1) Move the files from /2.0/ to /2.0.0.0/ for all locales on the website
2) Or add a redirect to send the start page and release notes that contain a version string of 2.0.0.0 over to /2.0/?

Comment 1

[Reed Loden [:reed]]

I'd prefer #1, and that's what I will be doing. However, that will break all the older Thunderbird builds that use "2.0pre" or whatever. Is that ok?

Comment 2

[Scott MacGregor]

Paul, the 1.8 branch builds have a version string of 2.0pre, should I change the version in version.txt there to 2.0.0.4pre? (Not sure we are doing a 0.4 pre but if we did do a security release we usually sync up with the firefox version scheme and skip over any missing ones).

Comment 3

[J. Paul Reed [:preed]]

(In reply to comment #2)
> Paul, the 1.8 branch builds have a version string of 2.0pre, should I change
> the version in version.txt there to 2.0.0.4pre? (Not sure we are doing a 0.4
> pre but if we did do a security release we usually sync up with the firefox
> version scheme and skip over any missing ones).

That's a good question; are we skipping over the versions to match parity with Firefox? If so, we can do that.

We usually don't do version bumps until the product is released, though (just in case we need to do respins or whatever; it turns out that doesn't matter, because it's on a _MINIBRANCH, but it does reduce confusion in the community, because the version numbers aren't changing until the release happened).

Comment 4

[Scott MacGregor]

Reed, giving the choice, I'd rather break the in product pages on the branch nightlies in order to make the in product pages work for the RC look right. Worst case scenario, we can always revert the start page to the local start page on the mozilla 1.8 branch until we figure out our strategy there.

Comment 5

[Scott MacGregor]

or I'll change it to 2.0.0.0pre on the branch which would work still, right? 

Comment 6

[Reed Loden [:reed]]

(In reply to comment #5)
> or I'll change it to 2.0.0.0pre on the branch which would work still, right? 

Correct. Just 2.0pre would be broken. 2.0.0.0pre would still be redirected to 2.0.0.0.

Comment 7

[Scott MacGregor]

Reed, I have some changes to the thunderbird 2 release notes I was going to check in, should i hold off on doing that until the release notes have been moved to /2.0.0.0/?

Comment 8

[Reed Loden [:reed]]

(In reply to comment #7)
> Reed, I have some changes to the thunderbird 2 release notes I was going to
> check in, should i hold off on doing that until the release notes have been
> moved to /2.0.0.0/?

Do it now, and just let me know when you're done. :)

Comment 9

[Scott MacGregor]

done! Those changes can get pushed out too when you move the files around. Thanks Reed.

Comment 10

[Reed Loden [:reed]]

Done. This change will go live tomorrow morning.

Comment 11

[Pascal Chevrel:pascalc]

please cc me on any change to the in-product pages, it has an impact on my work and on links on mozilla europe.

Thanks

Comment 12

[Paul Kim]

And please cc: Mary Colvig as well as the marketing contact here in the US.

Comment 13

[Scott MacGregor]

the start page and release notes are loading correctly now in the en-US RC builds. Thanks Reed!