Release Management/Release Notes Process: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 12: Line 12:


Note : Please make sure to only nominate those features and issues that are significant . [http://www.mozilla.org/en-US/firefox/21.0/releasenotes/ Sample] notes.
Note : Please make sure to only nominate those features and issues that are significant . [http://www.mozilla.org/en-US/firefox/21.0/releasenotes/ Sample] notes.
=== Updating Release Notes ===
All "Known Issues" (bugs) that do not have a fix date in the DB should be checked to see if they've subsequently been resolved in a newer Firefox version. This needs to happen on a weekly basis, since that's the cadence for Aurora/Beta.

Revision as of 18:55, 19 May 2013

This is a proposal for the process by which we construct release notes, but does not represent a final decision.

Release/Channel Specific Notes

Linked to "What's new" which appears on every channel's download page .
Eg : Check http://www.mozilla.org/en-US/firefox/new/ for latest Release and click on "What's new" below the green Firefox Download button to go to release notes

What's New/Known Issues Section Candidates

(channel) notes for Firefox(version) Desktop or Mobile are pulled from :

  • For features or known issues to be considered for release noting, set relnote-firefox: ?
  • We go through these release note nominations in a feature review meeting with various stake holders from product,project,marketing and other drivers where If we agree, we'll either set the flag to relnote-firefox:{version}+ for the first version of Firefox the feature will be present in, or just relnote-firefox:+ for known issues that will be noted until resolution
  • If we do not intend to release note something in any way, drivers will set relnote-firefox:-

Note : Please make sure to only nominate those features and issues that are significant . Sample notes.

Retrieved from "https://wiki.mozilla.org/index.php?title=Release_Management/Release_Notes_Process&oldid=657832"