|
| 1 | +### How to create a new devtools-components release for mozilla-central. |
| 2 | + |
| 3 | +Before you get started, you will need clones of devtools-components and mozilla-central, as well as |
| 4 | +a Bugzilla account. |
| 5 | + |
| 6 | +``` |
| 7 | +1. Prepare devtools-components release |
| 8 | + a. create a release branch on github |
| 9 | + b. update minor version in package.json, reset build version: |
| 10 | + v0.N.X -> v0.N+1.0 |
| 11 | + c. commit `release: bump devtools-components version to v0.N+1.0` |
| 12 | + d. create a PR on Github for this release |
| 13 | + e. make sure you have a configs/local.json file, with `firefox.mcPath` pointing to your mozilla-central clone |
| 14 | +
|
| 15 | +2. Copy to mozilla central |
| 16 | + a. update your mozilla-central clone to the latest |
| 17 | + b. in reps, run yarn copy-assets (or node bin/copy-assets.js)` |
| 18 | + c. create a new bug in Developer Tools: Shared Components [1] |
| 19 | + d. commit 'Bug XXXXXXX - devtools-components v0.N+1.0: update devtools-components bundle from GitHub;r=reviewer' |
| 20 | +
|
| 21 | +3. Validate & cleanup |
| 22 | + a. push to try, test locally, submit for review etc ... |
| 23 | + b. while try fails or some problem is detected, go back to devtools-components, fix the issue, |
| 24 | + create a new bundle and go back to 2.a |
| 25 | + c. when everything is fine and the patch is r+, land on autoland/inbound |
| 26 | + d. merge the PR on github |
| 27 | + e. create a tag for devtools-components-v0.N+1.0 on github |
| 28 | +``` |
| 29 | + |
| 30 | +After that any issue with the bundle should be addressed with a new build version. |
| 31 | +Ideally, if the bundle has to be updated in mozilla-central for a bugfix, a corresponding |
| 32 | +tag should be created on GitHub. |
| 33 | + |
| 34 | +[1] https://bugzilla.mozilla.org/enter_bug.cgi?product=Firefox&component=Developer%20Tools%3A%20Shared%20Components |
| 35 | + |
| 36 | + |
| 37 | +### How to publish a new devtools-components release to npm. |
| 38 | + |
| 39 | +Steps to publish to npm : |
| 40 | +``` |
| 41 | +1. Checkout the latest release tag |
| 42 | + a. git fetch --tags # get new tags from remote |
| 43 | + b. git checkout tags/devtools-components-v0.N+1.0 # checkout the tag created for the release |
| 44 | +2. npm login # Might ask your npm username and password |
| 45 | +3. npm publish |
| 46 | +``` |
| 47 | + |
| 48 | +To publish a new version of the package on npm, you need to : |
| 49 | + |
| 50 | +1. have an npm account and |
| 51 | +2. be a collaborator on the package. |
| 52 | + |
| 53 | +If you want to become a collaborator on the devtools-components package, please ask the other collaborators, either through IRC or Slack, or by filing an issue in this repo. |
0 commit comments