Release Management/Relnotes rules

This document is a draft.

This page describes the rules applied by the Release Team about the relnotes flag.

The release notes page lists all the new features, changes or unfixed critical bugs for a specific release of Firefox (desktop/mobile, beta/release, etc). Their edition and content are under the responsability of the release team.

For example:

• 27 Desktop release notes
• 28 Mobile beta release notes

User perspective: Adding an item in the release notes

To promote an item to be part of the release notes, the flag relnote-firefox should be used. This flag can be found in the Tracking Flags section.

While setting the flag, a description for the release note can be provided. Otherwise, the release team will look that the bug description or the commit message to find a correct description for the release note.

Release Team Perspective: Changing the relnote-firefox flag

Once a Mozillians has set the relnote-firefox flag to ?, the role of the release manager is to approve or reject its inclusion in the next release notes.

In case of rejection, the value - should be set and a comment left to explain the choice.

In case of acceptation, the item should be insert in the Nucleus database for a specific release (look for the field Target Milestone or Version to find out in which version it will be available). Then, set the relnote-firefox flag to the right version.