273
edits
Release Management/Release Notes: Difference between revisions
no edit summary
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
{{DISPLAYTITLE:The Firefox release notes process}} | {{DISPLAYTITLE:The Firefox release notes process}} | ||
<p style="font-size: larger; font-weight:bold;">This page explains how the release management team prepares release notes for Firefox.</p> | <p style="font-size: larger; font-weight:bold;">This page explains how the release management team prepares release notes for Firefox.</p> | ||
== About Firefox Release Notes == | == About Firefox Release Notes == | ||
Every four weeks, Firefox desktop and Firefox for Android release a new version of the browser. We publish release notes on [https://www.mozilla.org/firefox/releases/ mozilla.org] for an audience of web developers, tech press, and advanced and technical users of Firefox who want to be informed about the changes in Firefox's latest updates. | Every four weeks, Firefox desktop and Firefox for Android release a new version of the browser. We publish release notes on [https://www.mozilla.org/firefox/releases/ mozilla.org] for an audience of web developers, tech press, and advanced and technical users of Firefox who want to be informed about the changes in Firefox's latest updates. | ||
The release notes page lists notable new features, changes, or unfixed critical bugs for a specific release of Firefox. Adding release notes content is the responsibility of the release management team, as requested by engineering/product and reviewed by a product writer. | The release notes page lists notable new features, changes, or unfixed critical bugs for a specific release of Firefox. Adding release notes content is the responsibility of the release management team, as requested by engineering/product and reviewed by a product writer. | ||
See [https://wiki.mozilla.org/Release_Management/Release_Notes_Nomination Firefox Release Notes Nomination ] for information on how to nominate release notes for Firefox. | |||
Examples of past release notes: | Examples of past release notes: | ||
| Line 42: | Line 24: | ||
For questions on the process please reach out on [https://mozilla.slack.com/archives/C9L102H6X #release-notes] internal Slack channel. | For questions on the process please reach out on [https://mozilla.slack.com/archives/C9L102H6X #release-notes] internal Slack channel. | ||
== Summarized process == | |||
# Release management creates a Nightly release notes page in Nucleus for the upcoming version. | |||
# Release management makes the Nightly release notes public in Nucleus on Merge Day. | |||
# During the Nightly cycle, Release management monitors the relnote-firefox flag on Bugzilla and adds release notes for Nightly in Nucleus. | |||
# Release management creates a Beta release notes page in Nucleus for the upcoming version. | |||
# Release management copies applicable notes from the Nightly to the Beta release notes. | |||
# Release management makes the Beta release notes public in Nucleus after pushing Beta 1 live. | |||
# Release management shares a link to the Beta release notes on #release-notes. | |||
# During the Beta cycle, Release management monitors the relnote-firefox flag on Bugzilla and adds release notes for Beta in Nucleus. | |||
# Product writer creates a shared document for an editorial review and then shares it on #release-notes and to a mailing list. | |||
# Product writer copy-pastes notes from Beta Release Notes to the shared document. | |||
# Release management continues to monitor the relnote-firefox flag on Bugzilla and add release notes in Nucleus and the shared document. | |||
# Engineering/Product may add notes directly to the shared document. | |||
# Product writer performs an editorial review in the shared document. | |||
# Release management creates a release notes page in Nucleus for the upcoming version. | |||
# Release management copies the reviewed release notes from the shared document into Nucleus. | |||
# Release management adds links to security advisories and developer documentation for the release. | |||
# Release management shares a link to the staging release notes on #release-notes. | |||
# Release management makes the release notes public in Nucleus after pushing the Release live. | |||
== Gathering of notes during the cycle == | == Gathering of notes during the cycle == | ||