Release Management/Release Notes: Difference between revisions

Dot release information
m (Use a nicer title)
(Dot release information)
Line 114: Line 114:
Relevant information from the bug should be added as an item in the [https://nucleus.mozilla.org/ Nucleus database] for a specific release.
Relevant information from the bug should be added as an item in the [https://nucleus.mozilla.org/ Nucleus database] for a specific release.
Look for the "fixed" or "verified" flag in Bugzilla to make sure the issue is fixed for the first time in that release.
Look for the "fixed" or "verified" flag in Bugzilla to make sure the issue is fixed for the first time in that release.
=== Dot-Release Notes ===
There are a few specifics to notes for a dot-release.
Example: [https://www.mozilla.org/en-US/firefox/60.0.1/releasenotes/ 60.0.1 release notes]
* Notes '''do''' have the bug number indicated (and linked to) between parenthesis at the end, ex: ''WebVR has been disabled by default on macOS ([https://bugzilla.mozilla.org/show_bug.cgi?id=1459362 Bug 1459362])''
* Put a link to the reference release notes for the major version with this sentence, ex: ''Reference link to [https://www.mozilla.org/firefox/60.0/releasenotes/ 60.0 release notes]''
* In Nucleus make the note pointing to the reference mailing list as "release-specific" and don't associate any tag to it


=== Best practices for writing release notes ===
=== Best practices for writing release notes ===
Confirmed users
1,255

edits