Closed Bug 287477 Opened 19 years ago Closed 19 years ago

Release notes URL in Help welcome page and about: not updated to 1.0.x.html

Categories

(Firefox :: General, defect)

defect
Not set
minor

Tracking

()

RESOLVED DUPLICATE of bug 318991

People

(Reporter: lindyboi, Assigned: zbraniecki)

References

Details

(Keywords: relnote)

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050317 Firefox/1.0.2
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050317 Firefox/1.0.2

1.Open "Help Contents"
2.Click on "Release Notes" (web link)

Reproducible: Always

Actual Results:  
Takes user to
http://www.mozilla.org/products/firefox/releases/1.0.html


Expected Results:  
Should be
http://www.mozilla.org/products/firefox/releases/1.0.2.html

Presumably the release notes in the help should always be the ones in the
version released.
(In reply to comment #0)
> 1.Open "Help Contents"
> 2.Click on "Release Notes" (web link)

Help imports the URL from elsewhere:

http://lxr.mozilla.org/aviary101branch/source/browser/locales/en-US/chrome/global/brand.dtd#5

It appears that this location wasn't updated between releases, so consequently
it'll be wrong everywhere it's used.  (Currently, it's actually only used in two
places: Help contents and about:.)

Because localizations aren't actually supposed to change between releases, my
best guess is that the URL should be hardcoded but include a
build-time-generated version number.  The URL will be automatically updated for
the new release, and localizers won't have to do anything.

There's a possibility that I'll patch this as I describe above, but it's only a
possibility.

Anyway, moving to a more appropriate component...
Assignee: jwalden+fxhelp → firefox
Status: UNCONFIRMED → NEW
Component: Help Documentation → General
Ever confirmed: true
QA Contact: help-documentation → general
Summary: Browser help links to 1.0 release notes, should be 1.0.2 → Release notes URL not updated to 1.0.2 release notes URL
I worked with Chase to fix some 10 l10ns to not point to 1.0.html instead of
0.10.html. At that time, 1.0.html included the 1.0.1 release notes. But then Myk
split them up into 1.0.html, 1.0.1.html, and 1.0.2.html.

Maybe we should add a link at the top of 1.0.html to 1.0.2.html.

Trunk location of brand.dtd is:
http://lxr.mozilla.org/seamonkey/source/other-licenses/branding/firefox/locales/en-US/brand.dtd#5
OS: Windows XP → All
Hardware: PC → All
I meant: point to 1.0.html and not to 0.10.html.
*** Bug 288864 has been marked as a duplicate of this bug. ***
bug 288864 also notes that the release-notes link in the about: page wasn't updated.
Flags: blocking-aviary1.0.3?
Blocks: 286312
Summary: Release notes URL not updated to 1.0.2 release notes URL → Release notes URL in Help welcome page and about: not updated to 1.0.x.html
Keywords: relnote
Flags: blocking-aviary1.0.4?
taking.
rebron: can I assume that we will have webpage for all versions like
releases/1.0.html, releases/1.0.1.html, releases/1.0.3.html, releases/1.1.1.html
and so on?
Assignee: firefox → gandalf
Flags: blocking-aviary1.0.3?
No patch, not blocking the release
Flags: blocking-aviary1.0.5? → blocking-aviary1.0.5-
See bug 282070 for an example of release notes URL bumping.
bsmedberg recommended the following course of action to deal with release note
URL changes *AND* localization issues of same:

* remove the URL from brand.dtd (and brand.properties);
* use instead a string pref in firefox.js. This pref could still be overridden
(if necessary) in firefox-l10n.js for localization;

The new release note URL would be akin to:
 http://www.mozilla.org/projects/firefox/release.html?locale=%LOCALE%&version=%VERSION%
The Help welcome page doesn't contain the release notes link anymore.
I've fixed the link in about: in bug 318991, so duping to that bug.


*** This bug has been marked as a duplicate of 318991 ***
No longer blocks: 286312
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.