Jetpack/Release Process: Difference between revisions

Jetpack/Release Process (view source)

505 bytes added , 22 December 2011

Confirmed users

1,100

edits

@@ Line 384: / Line 384: @@
 [PROPOSED]
-Requirements: working checkout of AMO-validator & prerequisites. Please see the [https://github.com/mozilla/amo-validator/blob/master/README.rst AMO Validator Readme] for the gory details.
+Requirements: working checkout of AMO-validator & prerequisites. Please see the [https://github.com/mozilla/amo-validator/blob/master/README.rst AMO Validator Readme] for the gory details. We should fork the amo-validator repo and then for each release do the following:
-<pre>cd jetpack
+Step 1: update the hash file in our forked repo:
+<pre>
+git pull mozamo master # update from the upstream 'mozamo' repo
+cd jetpack
 ./generate_jp_whitelist.sh
 cd ../
@@ Line 393: / Line 396: @@
 git push origin master</pre>
-Once this is done, AMO will need to push these changes to the live site so that the validator supports the new version of the SDK.
+Step 2: We issue a pull request to the mozilla/amo-validator and <del>pester</del> engage the AMO devs to accept our updated hash file.
+Step 3: We do some testing on AMO's existing test infrastructure on allizom.com. The test should be essentially:
+* run the validator on xpi files that use the new version
+* ensure the validator does not raise errors on SDK core files.
+Step 4: The changes are pushed with the regular Thursday AMO push.
 == Update Latest Builds Redirect ==