Closed Bug 540264 Opened 16 years ago Closed 16 years ago

[404] Thunderbird v3.0.1 release notes

Categories

(www.mozilla.org Graveyard :: Thunderbird, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: wicked, Unassigned)

References

()

Details

+++ This bug was initially created as a clone of Bug #531020 +++ My Thunderbird 3.0 (Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.5) Gecko/20091204 Thunderbird/3.0) just told me there's v3.0.1 available. Unfortunately, when I click "View more information about this update" link to see why should I update (mostly looking for list for security bugs fixed and full buglist of fixes) I was greeted with a 404 error. It took me to the http://www.mozillamessaging.com/en-US/thunderbird/3.0.1/releasenotes/ URL. Looks like same error affected 3.0 release also. Should your release process contain a delay to make sure website updates are done before you start pushing updates to clients?
Bah, looks like I had beta channel selected due to having first installed "3.0 beta 4" instead of the final 3.0 version. Changing to release channel (clumsily via editing the JS file directly under "Program Files") made the update notifications go away so no wonder there's no release notes yet. Hopefully they're there once final 3.0.1 is released. I'm sorry for the confusion!
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → INVALID
(In reply to comment #1) > Bah, looks like I had beta channel selected due to having first installed "3.0 > beta 4" instead of the final 3.0 version. Changing to release channel (clumsily > via editing the JS file directly under "Program Files") made the update > notifications go away so no wonder there's no release notes yet. Hopefully > they're there once final 3.0.1 is released. I'm sorry for the confusion! No problem ;-) You can stay on the beta channel too !
Product: Websites → www.mozilla.org
Product: www.mozilla.org → www.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.