Closed Bug 406248 Opened 18 years ago Closed 18 years ago

The 2.0.0.11 release notes don't say what actually got fixed since 2.0.0.10

Categories

(Infrastructure & Operations Graveyard :: WebOps: Other, task)

task
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: justdave, Assigned: justdave)

References

()

Details

At all. Not even a little clue or where else to look. As an end user seeing an update a week after the last one, I need to be convinced why I should upgrade *again*. The release notes in their existing form are incredibly unconvincing. The last non-security update we did (2.0.0.9) is a good example to look at for how this could have been dealt with. http://www.mozilla.com/en-US/firefox/2.0.0.9/releasenotes/
Saying something simple like "fixes a compatibility issue with some websites" might be enough. Just saying "we fixed something" (which is essentially what the existing one says) is pretty unconvincing and sounds like we're trying to hide something.
Second that. I'm a normal end user and I always check the release notes to see what gets fixed before updating. This time, I can't tell. It's disturbing and is wasting my time.
There are comments in hendrix that complain about the same thing: Comments: The release notes for 2.0.0.11 say only "This release corrects a problem that was found in the previous release, Firefox 2.0.0.10." http://en-us.www.mozilla.com/en-US/firefox/2.0.0.11/releasenotes/ Please provide a link to the details of what was fixed? I need to know if this will affect all the machines I've just updated to 2.0.0.10, and I can't find the details of the actual problem anywhere. Comments: the release notes page at http://en-us.www.mozilla.com/en-US/firefox/2.0.0.11/releasenotes/ says this release does the following: "corrects a problem that was found in the previous release". Aren't all releases to correct problems that were found in previous releases? What exactly was the problem discovered? There is no link to read the details. Are you too embarrassed to list it? Don't treat your users like complete idiots. Some of us aren't. Some of us READ what the fixes are and decided whether or not we need them. This release report is without ANY content! michael
Normally "me too" is unhelpful for discussions, but I'm not sure how else this sentiment's popularity cam be registered. As an end user I would also like more detail on the _why_ and _what_ of releases. At least _some_ detail.
2.0.0.11 broke my install. only loads in safe mode now. bug submitted.
/en-US/firefox/2.0.0.11/releasenotes/index.html Completed: At revision: 8423 Added a link to the bug.
/en-US/firefox/2.0.0.11/releasenotes/index.html Completed: At revision: 8423 Apparently my first fix didn't meet with the approval of the masses.
Assignee: beltzner → justdave
Component: www.mozilla.com → Server Operations: Web Content Push
Product: Websites → mozilla.org
QA Contact: www-mozilla-com → justin
Version: unspecified → other
U en-US/firefox/2.0.0.11/releasenotes/index.html Updated to revision 8425. NS cache flushed as well, should be live.
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
(In reply to comment #9) > NS cache flushed as well, should be live. > is now live -> verified
Status: RESOLVED → VERIFIED
Component: Server Operations: Web Operations → WebOps: Other
Product: mozilla.org → Infrastructure & Operations
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.