Jetpack/Release Process: Difference between revisions

Jetpack/Release Process (view source)

491 bytes removed , 29 April 2010

canmove, Confirmed users

2,056

edits

@@ Line 119: / Line 119: @@
 To update the website, clone its code from the [https://hg.mozilla.org/labs/jetpack/ old Jetpack Prototype repository] (the code lives in the [https://hg.mozilla.org/labs/jetpack/file/tip/website website subdirectory]), change the code as needed, test your changes by loading your local working copy of the code in your browser, commit your changes, tag the changeset with the "website-production" tag (you'll need to specify <tt>-f</tt> to force Mercurial to update the existing tag), and push your changes back to the central repository.
-=== Push Documentation ===
-Documentation lives on the website in /sdk/[VERSION]/docs/ directories (with a redirect from /sdk/latest/docs/ to the latest version's docs), but the process for pushing a new version's docs to the website is different than for other pages on the site.
-To push a new version's docs to the website, ask Zandr to do it. (We should make this process more generic.)
-{{note|don't update the "latest" redirect in this step. That should happen in the Release step.}}
 === Write Blog Post ===