diff options
| author | kumavis <kumavis@users.noreply.github.com> | 2018-06-04 03:25:43 +0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2018-06-04 03:25:43 +0800 |
| commit | 123d74c4b2e2062d2ce0b50fbe86129e15473b8f (patch) | |
| tree | 269f009a3447377dd23e704232f3663dafd1739f | |
| parent | a08e58f0fdc3f2377cd35b8557828161bff3f7b7 (diff) | |
| parent | 4cc2273c20a62745368c668ef09ec4239ec59090 (diff) | |
| download | tangerine-wallet-browser-123d74c4b2e2062d2ce0b50fbe86129e15473b8f.tar tangerine-wallet-browser-123d74c4b2e2062d2ce0b50fbe86129e15473b8f.tar.gz tangerine-wallet-browser-123d74c4b2e2062d2ce0b50fbe86129e15473b8f.tar.bz2 tangerine-wallet-browser-123d74c4b2e2062d2ce0b50fbe86129e15473b8f.tar.lz tangerine-wallet-browser-123d74c4b2e2062d2ce0b50fbe86129e15473b8f.tar.xz tangerine-wallet-browser-123d74c4b2e2062d2ce0b50fbe86129e15473b8f.tar.zst tangerine-wallet-browser-123d74c4b2e2062d2ce0b50fbe86129e15473b8f.zip | |
Merge pull request #4353 from MetaMask/publishing-guide-update
Update publishing guide
| -rw-r--r-- | docs/publishing.md | 28 |
1 files changed, 21 insertions, 7 deletions
diff --git a/docs/publishing.md b/docs/publishing.md index 3022b7eda..45662900d 100644 --- a/docs/publishing.md +++ b/docs/publishing.md @@ -2,18 +2,32 @@ When publishing a new version of MetaMask, we follow this procedure: +## Preparation + +We try to ensure certain criteria are met before deploying: + +- Deploy early in the week, to give time for emergency responses to unforeseen bugs. +- Deploy early in the day, for the same reason. +- Make sure at least one member of the support team is "on duty" to watch for new user issues coming through the support system. +- Roll out incrementally when possible, to a small number of users first, and gradually to more users. + ## Incrementing Version & Changelog Version can be automatically incremented [using our bump script](./bumping-version.md). npm run version:bump $BUMP_TYPE` where `$BUMP_TYPE` is one of `major`, `minor`, or `patch`. -## Publishing +## Building -1. `npm run dist` to generate the latest build. -2. Publish to chrome store. - - Visit [the chrome developer dashboard](https://chrome.google.com/webstore/developer/dashboard?authuser=2). -3. Publish to firefox addon marketplace. -4. Post on Github releases page. -5. `npm run announce`, post that announcement in our public places. +While we develop on the main `develop` branch, our production version is maintained on the `master` branch. + +With each pull request, the @MetaMaskBot will comment with a build of that new pull request, so after bumping the version on `develop`, open a pull request against `master`, and once the pull request is reviewed and merged, you can download those builds for publication. + +## Publishing +1. Publish to chrome store. +2. Visit [the chrome developer dashboard](https://chrome.google.com/webstore/developer/dashboard?authuser=2). +3. Publish to [firefox addon marketplace](http://addons.mozilla.org/en-us/firefox/addon/ether-metamask). +4. Publish to [Opera store](https://addons.opera.com/en/extensions/details/metamask/). +5. Post on [Github releases](https://github.com/MetaMask/metamask-extension/releases) page. +6. Run the `npm run announce` script, and post that announcement in our public places. |