| 1 | This document includes:
|
| 2 | - how to make npm, github release of remix-* packages
|
| 3 | - how to update remix.ethereum.org.
|
| 4 | - how to update remix-alpha.ethereum.org.
|
| 5 |
|
| 6 | # remix-* release (npm release, github release)
|
| 7 |
|
| 8 | - For a specifix module (lib/core/debug/ide/solidity/tests)
|
| 9 | - In a new branch, bump the version in package.json, push it and create PR.
|
| 10 | - Wait for tests completion.
|
| 11 | - merge PR
|
| 12 | - build the branch ( `npm run build` for remix-ide ).
|
| 13 | - execute `npm publish`.
|
| 14 | - create new `tag` ( e.g `git tag v0.6.1-alpha.2` ).
|
| 15 | - push the tag ( `git push --tag` ).
|
| 16 | - execute `gren changelog --generate -t <new tag>..<previous tag> --data-source=prs`.
|
| 17 | - in `changelog.md` remove the closed and non merged PR.
|
| 18 | - publish a release in github using the changelog.
|
| 19 |
|
| 20 |
|
| 21 | # remix.ethereum.org update
|
| 22 |
|
| 23 | This is not strictly speaking a release. Updating the remix site is done through the Travis build:
|
| 24 |
|
| 25 | - In remix-ide repository
|
| 26 | - Switch to the branch `remix_live`
|
| 27 | - Rebase the branch against master
|
| 28 | - Force push
|
| 29 | - https://travis-ci.org/ethereum/remix-ide
|
| 30 | - Click `More options`
|
| 31 | - Click `Trigger build`
|
| 32 | - Select `remix_live`
|
| 33 | - Click `Trigger custom build`
|
| 34 | - Once the build is finished (can take a while) and successful, check remix.ethereum.org is updated accordingly
|
| 35 |
|
| 36 | # remix-alpha.ethereum.org update
|
| 37 |
|
| 38 | This is not strictly speaking a release. Updating the remix-alpha site is done through the Travis build:
|
| 39 |
|
| 40 | - https://travis-ci.org/ethereum/remix-ide
|
| 41 | - Click `More options`
|
| 42 | - Click `Trigger build`
|
| 43 | - Select `Master`
|
| 44 | - Click `Trigger custom build`
|
| 45 | - Once the build is finished (can take a while) and successful, check remix-alpha.ethereum.org is updated accordingly
|
| 46 |
|
| 47 | # beta testing remix
|
| 48 |
|
| 49 | We publish a new release roughly every month and greatly appreciate support on beta testing.
|
| 50 |
|
| 51 | By giving report, beta testers help to:
|
| 52 | - verify viabilty (in term core and UX design) of new features
|
| 53 | - track possible regression
|
| 54 | - propose new update
|
| 55 | - contribute on reviewing / building Pull Request
|
| 56 |
|
| 57 | Current Beta testers:
|
| 58 |
|
| 59 |
|