Release Management/Release Notes: Difference between revisions

Release Management/Release Notes (view source)

Revision as of 17:18, 25 September 2015

1,038 bytes added , 25 September 2015

m

→‎Release Notes: further info on relnotes

Lizhenry

Confirmed users

2,816

edits

@@ Line 1: / Line 1: @@
 =Release Notes=
-The release notes are managed through the [[Websites/Mozilla.org/Publishing|Nucleus interface]] available on https://nucleus.mozilla.org/.
+==What's the purpose of release notes?==
+Release notes are a central source of information about changes in each Firefox release. They're mainly aimed at advanced and technical users of Firefox who want to be informed about the changes in Firefox's latest updates. They may be web developers, IT managers who deploy Firefox for their users, or people who need to know all the details of the browser they use to accomplish their work.  Technical journalists also follow our release notes in order to write stories on changes in Firefox.
-Developers or other contributors can nominate fixes or changes for release notes. If your fix should be in release notes, tell us what it did, what it means, and what the users and tech press should know. Ideally, we link from each note to an MDN page, a blog post hosted somewhere on mozilla.org, or even a wiki page for users to understand changes, fixes, and new features.
+==How you can help with release notes==
+;1. Nominate fixes and features!
+Anyone can go to a bug in bugzilla.mozilla.org, and nominate fixes or changes for release notes. Open the "Tracking Flags" menu on the right side of the page. Then please set the relnote-firefox: flag to "?". Release management checks this flag regularly.
-Release notes use the tracking flag ''relnote-firefox:''. By default, the value "?" is going to be set and some information requested (wording proposed, documentation/URL, etc). Release management checks this flag regularly.
+A form will pop up in the Bugzilla comments box, asking for your suggested wording for the note and an optional url to link to further documentation.
-Release management sometimes skims through the whole list of fixed bugs for a release to find possible release notes. We ask engineering managers and developer teams to tell us what note-worthy fixes are upcoming for aurora, beta, and release channels. We also check hacks.mozilla.org.
+;2. Explain the fix
+If your fix or other project should be in release notes, tell us what it did, what it means, and what the users and tech press should know. Ideally, we link from each note to an MDN page, a blog post hosted somewhere on mozilla.org, or even a wiki page for users to understand changes, fixes, and new features.
-Notable fixes and new features can also be found at https://developer.mozilla.org/en-US/Firefox/Releases
+==What release managers do for relnotes==
+Release management may skim through the entire list of fixed bugs for a release to find possible release notes. That's often around 4000 bugs!
+We also ask engineering managers and developer teams to tell us what note-worthy fixes are upcoming for aurora, beta, and release channels. We  check other sources like hacks.mozilla.org to find notable new work. In every release cycle, relman asks people on several engineering mailing lists to read release note drafts, review them, and suggest changes.
+The release notes are written and managed in the [[Websites/Mozilla.org/Publishing|Nucleus interface]] available on https://nucleus.mozilla.org/.
+Notable fixes and new features in more detail for developers can be found at https://developer.mozilla.org/en-US/Firefox/Releases
 ==Aurora and Beta Cycles==