canmove, Confirmed users
2,056
edits
Jetpack/Release Process: Difference between revisions
Jump to navigation
Jump to search
→Notify Relevant Parties
| Line 52: | Line 52: | ||
Notify the product delivery team about the release by adding a summary of its goals, status of the release candidates, and tentative release date to the [[Firefox/DeliveryMeetings|weekly meeting]] notes. Attend the weekly meeting and talk about the release if asked to do so. | Notify the product delivery team about the release by adding a summary of its goals, status of the release candidates, and tentative release date to the [[Firefox/DeliveryMeetings|weekly meeting]] notes. Attend the weekly meeting and talk about the release if asked to do so. | ||
=== Notify IT === | |||
IT is responsible for pushing changes to the website (including new versions of the documentation) to production, and they should be notified in advance that such changes are forthcoming, even though they don't actually push the changes until the day of the release. | |||
To notify them, [https://bugzilla.mozilla.org/enter_bug.cgi?product=mozilla.org&format=itrequest&cc=:zandr file an IT request], cc:ing ":zandr", to have the website changes pushed to production, including: | |||
# pushing the new version's docs to the website; | |||
# updating the /sdk/latest/docs/ redirect to point to the new version's docs; | |||
# pushing the files in the changeset tagged "website-production" in the "website" subdirectory in the repository https://hg.mozilla.org/labs/jetpack to the production server. | |||
Make sure to note that the work shouldn't be done until the day of the release, specify the tentative release date, and update it if it changes. | |||
== Build/Test Release Candidate(s) == | == Build/Test Release Candidate(s) == | ||