478657 - Default home page information incorrect

Status: RESOLVED FIXED

(SeaMonkey :: Website, defect)

Description

[Mariane]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1b3pre) Gecko/20081202 SeaMonkey/2.0a2
Build Identifier: SeaMonkey/2.0a2

I just downloaded and installed SeaMonkey 2.0 (alpha)

When it is run for the first time, it displays a page 
which seemingly identifies it as an old version of 
SeaMonkey 1.1.14

So something seems to be wrong with the information 
it is sending out about itself. 





Reproducible: Always

Steps to Reproduce:
1. Use SeaMonkey version 2.0
2. Go to http://www.seamonkey-project.org/start/
3. Read what it says
Actual Results:  
It says: 
Hey! Your copy of SeaMonkey is more than four weeks old. 
(...)

So if you're not running the latest release (SeaMonkey 1.1.14)
(...)


Expected Results:  
You are running SeaMonkey 2.0
(...)

It should identify the browser version with no mistakes.

Comment 1

[Robert Kaiser]

This is no real bug.

1) "You are running SeaMonkey 2.0" would be straight out wrong, as you are using a testing (alpha) version of it.
2) "the latest release" actually _is_ SeaMonkey 1.1.14, at least the latest stable one.
3) 2.0 Alpha 2 _is_ than four weeks old and therefore a somewhat dated testing version, even if we haven't released a newer one yet.

Comment 2

[Mariane]

Whether it's a testing version or a stable release, I'm still running it, 
or something is wrong with my undertanding of English (which is quite 
possible). 

Anyway, it will eventually become the current version, so at one point 
the identification bug will have to be fixed. Why not now? 

Mariane

Comment 3

[Robert Kaiser]

(In reply to comment #2)
> Anyway, it will eventually become the current version, so at one point 
> the identification bug will have to be fixed. Why not now? 

It will not become the "current version", if you mean a stable release, as the stable release that will be based on this alpha will actually have different version and Gecko date identifiers, both of which will make us not trigger this warning.

Comment 4

[Mariane]

Really? I thought these things just went from trial version to stable 
version. So I have learn something today :-). And mine went from 2.0 
to 2.0.1 today. 

In this case I guess it's not important to fix this bug. 

By the way, I like it very much, it's the first I've seen which displays 
phpBB forums version 3 properly. Congratulations. 

Mariane

Comment 5

[Robert Kaiser]

You might be mistaking our version identifiers ;-)

"2.0a2" means "2.0 Alpha 2" (a is for Alpha), and e.g. "2.0b1pre" means "a preview" (that's the "pre" part) of "2.0 Beta 1" (b is for Beta).

Final, stable versions don't have any letters in their version identifiers, only numbers.

Any builds with "pre" in the version are highly experimental, mostly untested and may break or destroy data at any time because of bugs, so care to have backups of all data when using those.
Any versions without a "pre" but with an "a" or "b" in the identifier are still potentially unstable, but somewhat pre-tested to actually work for many usual operations and are thought for widespread testing, but not mass-production use.

Comment 6

[Philip Chee]

Based on Comment #1 resolving as INVALID

Comment 7

[Robert Kaiser]

Philip, I had intentionally not closed this bug, as I still kept it in mind for attacking some day - it's really not nice to tell users of our latest prerelease that they're running an old copy.

I just added some code to make this experience smoother.