273
edits
Release Management/Release Notes: Difference between revisions
Release Management/Release Notes (view source)
Revision as of 14:43, 6 December 2023
, 6 December 2023Included steps for when adding a release note in Nucleus with a rollout
No edit summary |
(Included steps for when adding a release note in Nucleus with a rollout) |
||
| (3 intermediate revisions by 2 users not shown) | |||
| Line 129: | Line 129: | ||
** Use the Community category when adding the release note. | ** Use the Community category when adding the release note. | ||
* Review the draft release notes document. | * Review the draft release notes document. | ||
* Inform the Release Management team the document is ready for peer review. | |||
** Another member of the team will review the release notes for clarity and/or to suggest improvements. | |||
* Create a new release in Nucleus for Desktop, Android, and iOS. | * Create a new release in Nucleus for Desktop, Android, and iOS. | ||
* Add release notes from the draft release notes document. | * Add release notes from the draft release notes document. | ||
| Line 134: | Line 136: | ||
** Order the release notes via the ''sort num'', the order will be from highest number to lowest. Otherwise, the default order is based when the release notes were added to the release. | ** Order the release notes via the ''sort num'', the order will be from highest number to lowest. Otherwise, the default order is based when the release notes were added to the release. | ||
** Group items that belong to a category in the same order. For example, items with WebRTC can be grouped together. | ** Group items that belong to a category in the same order. For example, items with WebRTC can be grouped together. | ||
** If the release note covers a feature that is part of a rollout and not enabled by default then enable '''Progressive rollout'''. | |||
*** If rollout is only targetted at specific countries then select ''Relevant countries'' from the list of '''Available relevant countries''' | |||
* Set the relnote tracking flag to XXX+ | * Set the relnote tracking flag to XXX+ | ||
* Share a link to the staged Release Notes on [https://mozilla.slack.com/archives/C9L102H6X #release-notes] internal Slack channel. | * Share a link to the staged Release Notes on [https://mozilla.slack.com/archives/C9L102H6X #release-notes] internal Slack channel. | ||
| Line 233: | Line 237: | ||
** Image URL: 'https://www.mozilla.org/media/img/firefox/releasenotes/note-images/115_devtools.png' | ** Image URL: 'https://www.mozilla.org/media/img/firefox/releasenotes/note-images/115_devtools.png' | ||
** Release Note: https://nucleus.mozilla.org/admin/rna/note/789608/change/ | ** Release Note: https://nucleus.mozilla.org/admin/rna/note/789608/change/ | ||
* The <code><img></code> tag can also be used, which also allows the use of <code>height</code> and <code>width</code> attributes if resizing is necessary. | |||
** NOTE: The <code>height</code> and <code>width</code> attributes <b>must</b> be specified before the <code>alt</code> attribute or the image will not appear in the preview pane. It will still appear as expected in Bedrock, however. | |||
[[category:Release_Management|Release Notes]] | [[category:Release_Management|Release Notes]] | ||
[[category:Release_Management:Processes|Release Notes]] | [[category:Release_Management:Processes|Release Notes]] | ||