[x] Ask for a push of product-details to production once we have all the locales built
[x] Copy the previous release notes template in Nucleus with the new version number
During the cycle:
[x] Add that we watch all commits for interesting features
[x] Add that interesting changes should be communicated to our alpha-testers via Twitter
[x] Interesting features visible to the end user should have the relnote flag set
[x] Write Release Notes on the fly
[x] Watch reports on Twitter, IRC and other communication channels about major regressions. Ask for backout of a patch if the end-user impact may lead to loosing alpha testers.
End of cycle:
[x] Check that there is no visual regression on the WNP caused by template changes on mozilla.org or gecko changes a week before merge day
https://wiki.mozilla.org/index.php?title=Release_Management/Nightly&oldid=1136006
This page lists the tasks for RelMan during the Nightly cycle Beginning of a new cycle
During the cycle:
End of cycle: