[x-post to dev.planning and dev.platform]
In relation to release notes process, we've gotten a couple of pieces of
feedback in recent memory:
1) It's not clear how to mark something as a release notes candidate (some have
used the relnote keyword in the past)
2) It's not clear whether something will actually be noted
3) Sometimes a feature or known issue is (correctly or otherwise) release noted
without devs being aware
We're creating a new tracking flag to resolve all three of these issues. You'll
now find relnote-firefox on any bug that can be nominated for tracking. If
you'd like a feature or known issue considered for release noting, just set
relnote-firefox:?. If we agree, we'll either set the flag to
relnote-firefox:{version}+ for the first version of Firefox the feature will be
present in, or just relnote-firefox:+ for known issues that will be noted until
resolution. If we do not intend to release note something in any way, drivers
will set relnote-firefox:-.
Please make sure to only nominate those features and issues that are
significant. See https://www.mozilla.org/en-US/firefox/18.0.2/releasenotes/ for
an example of recent notes.
-Alex
_______________________________________________
dev-platform mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-platform
