canmove, Confirmed users
2,056
edits
Jetpack/Release Process: Difference between revisions
Jump to navigation
Jump to search
→Prepare to Release
| Line 29: | Line 29: | ||
Preparing to release involves doing three different sets of things, which can be done in parallel: | Preparing to release involves doing three different sets of things, which can be done in parallel: | ||
* file tracking bugs | |||
* notify relevant parties | * notify relevant parties | ||
* build/test release candidate(s) | * build/test release candidate(s) | ||
* create marketing/PR/evangelism materials | * create marketing/PR/evangelism materials | ||
== File Tracking Bugs == | |||
File a bug to track code blockers of the release and another to track the overall release. | |||
* [https://bugzilla.mozilla.org/enter_bug.cgi?bug_status=ASSIGNED&assigned_to=myk@mozilla.org&cc=dietrich%40mozilla.com&comment=This%20bug%20tracks%20code%20blockers%20for%20the%20Jetpack%20SDK%20x.x%20release.%20%20Ping%20Myk%20or%20Dietrich%2C%20or%20comment%20here%20in%20this%20bug%2C%20to%20nominate%20a%20bug%20to%20block%20the%20release.&component=Jetpack%20SDK&op_sys=All&priority=--&product=Mozilla%20Labs&rep_platform=All&short_desc=x.x%20release%20blocker%20bugs code blockers bug template] | |||
* [https://bugzilla.mozilla.org/enter_bug.cgi?bug_file_loc=https%3A%2F%2Fwiki.mozilla.org%2FLabs%2FJetpack%2FSDK%2Fx.x%2FRelease&bug_status=ASSIGNED&cc=dietrich%40mozilla.com&comment=We%20should%20release%20Jetpack%20SDK%20x.x.%20%20Use%20this%20bug%20to%20track%20tasks%20that%20need%20to%20be%20done%20to%20release%20the%20product%2C%20like%20spinning%20candidate%20builds%20and%20publishing%20a%20blog%20post%20about%20it.%20%20Use%20bug%20(code%20blockers%20bug%20number)%20to%20track%20code%20blockers%20for%20the%20release.&component=Jetpack%20SDK&op_sys=All&product=Mozilla%20Labs&rep_platform=All&short_desc=release%20Jetpack%20SDK%20x.x&assigned_to=myk@mozilla.org&dependson=(code%20blockers%20bug%20number) release bug template] | |||
== Notify Relevant Parties == | == Notify Relevant Parties == | ||
| Line 57: | Line 65: | ||
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. | 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& | To notify them, file an IT request ([https://bugzilla.mozilla.org/enter_bug.cgi?blocked=(release%20bug%20number)&bug_status=NEW&cc=zandr%40mozilla.com&comment=We%20are%20now%20stabilizing%20the%20Jetpack%20SDK%20source%20tree%20in%20preparation%20for%20the%20release%20of%20Jetpack%20SDK%20x.x.%20%20When%20it%20is%20time%20to%20release%2C%20the%20corresponding%20changes%20to%20its%20website%20should%20be%20pushed%20to%20production%2C%20including%3A%0a%0a1.%20pushing%20the%20new%20version%27s%20docs%20to%20the%20website%3B%0a2.%20updating%20the%20%2Fsdk%2Flatest%2Fdocs%2F%20redirect%20to%20point%20to%20the%20new%20version%27s%20docs%3B%0a3.%20pushing%20the%20files%20in%20the%20changeset%20tagged%20%22website-production%22%20in%20the%22website%22%20subdirectory%20in%20the%20repository%20https%3A%2F%2Fhg.mozilla.org%2Flabs%2Fjetpack%20to%20the%20production%20server.%0a%0aNote%3A%20this%20work%20should%20not%20be%20done%20until%20the%20day%20of%20the%20release.%20%20The%20tentative%20release%20date%20is%20currently%20Wednesday%2C%20(Month%20and%20Date).&component=Server%20Operations%3A%20Web%20Content%20Push&op_sys=All&product=mozilla.org&rep_platform=All&short_desc=push%20Jetpack%20SDK%20x.x%20website%20changes%20to%20production IT request bug template]), cc:ing ":zandr", to have the website changes pushed to production, including: | ||
# pushing the new version's docs to the website; | # pushing the new version's docs to the website; | ||