Jetpack/Release Process: Difference between revisions

Line 434: Line 434:
# File a bug [https://bugzilla.mozilla.org/enter_bug.cgi?product=addons.mozilla.org|against AMO] with the 'Add-on Builder' component, to add the new version to production.
# File a bug [https://bugzilla.mozilla.org/enter_bug.cgi?product=addons.mozilla.org|against AMO] with the 'Add-on Builder' component, to add the new version to production.
# in a branch of your forked repo for Flightdeck, make changes using [https://github.com/mozilla/FlightDeck/pull/156|pull request 156] as a template and then issue a pull request against Flightdeck.
# in a branch of your forked repo for Flightdeck, make changes using [https://github.com/mozilla/FlightDeck/pull/156|pull request 156] as a template and then issue a pull request against Flightdeck.
# get IT / Flightdeck to run the 'add sdk'[1] command on -dev, make sure things work
# ensure that seanmonstr / zalun / arron accepts the pull request and tags it. IT can then take this tag and complete the deployment.
# get IT to run the 'add sdk'[1] command on -dev, make sure things work. Also, stephend should be pinged to ensure tests pass on -dev with the new revision.
# Schedule a push with IT and push the site
# Schedule a push with IT and push the site
# Run the add sdk command in production
# Run the add sdk command in production
Confirmed users
1,100

edits