Closed Bug 733483 Opened 13 years ago Closed 10 years ago

Release notes' "(First offered to … channel users on" date indication doesn't mention the version number (what was offered)

Categories

(www.mozilla.org :: Pages & Content, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: Aleksej, Assigned: Sylvestre)

References

(Blocks 1 open bug)

Details

Release notes mention a date: https://www.mozilla.org/en-US/firefox/10.0beta/releasenotes/ “Notes (First offered to Beta channel users on November 22nd, 2011)” http://www.mozilla.org/en-US/firefox/10.0/releasenotes/ “Notes (First offered to release channel users on January 31, 2012)” http://www.mozilla.org/en-US/firefox/10.0.1/releasenotes/ “Notes (First offered to release channel users on February 10, 2012)” http://www.mozilla.org/en-US/firefox/10.0.2/releasenotes/ “Notes (First offered to release channel users on February 16, 2012)” That’s unclear, especially in case of Beta. In all cases, that phrase refers to a particular stable version, but it doesn’t mention the version number. That’s the bug. In case of Beta, it’s worse, because there are multiple Betas, and this date refers to the first one only.
Component: www.mozilla.org/firefox → www.mozilla.org
Component: www.mozilla.org → General
Product: Websites → www.mozilla.org
Severity: minor → normal
How do I find what's new in Beta 2 or Beta 3 compared to Beta 1 at all?
Component: General → Pages & Content
OS: Linux → All
Hardware: x86_64 → All
This bug is fixed: Example: https://www.mozilla.org/en-US/firefox/33.0/releasenotes/ Version 33.0, first offered to Release channel users on October 13, 2014 https://www.mozilla.org/en-US/firefox/34.0beta/releasenotes/ Version 34.0beta, first offered to Beta channel users on October 16, 2014 (In reply to [:Aleksej] from comment #1) > How do I find what's new in Beta 2 or Beta 3 compared to Beta 1 at all? See this blog: http://release.mozilla.org/
Assignee: nobody → sledru
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.