parent
c4bd3df6c7
commit
e93976115a
@ -1,26 +1,55 @@ |
|||||||
# Release process |
# Release process |
||||||
This document details steps for publishing packages and tag the code base accordingly: |
|
||||||
|
This document includes: |
||||||
|
- how to update remix.ethereum.org. |
||||||
1) Publish (using lerna) all the modules that depends on one of the newly published module |
- how to update remix-alpha.ethereum.org. |
||||||
|
- how to release remix IDE. |
||||||
- checkout a new branch from master |
|
||||||
- npm run publish (that command use lerna) |
## Remix libs release |
||||||
- commit |
- TODO |
||||||
|
|
||||||
2) Increment the root (repository scoped) package.json |
## Remix IDE release |
||||||
|
|
||||||
- increment root package.json version |
- git fetch origin master |
||||||
- commit |
- git checkout origin/master |
||||||
- merge the branch |
- git checkout -b bumpVersion |
||||||
|
- update package.json version |
||||||
3) Create a tag (using the package.json version) |
- remove package-lock.json version and generate a new one with `npm install` |
||||||
|
- merge PR |
||||||
- checkout latest origin/master |
- git fetch origin master |
||||||
- npm run tag |
- git checkout origin/master |
||||||
- previousVersion=[previous_version] npm run updateChangelog |
- git tag v(version-number) |
||||||
- create a new release out of the changes of CHANGELOG.md |
- git push --tags |
||||||
|
- github-changes -o ethereum -r remix-ide -a --only-pulls --use-commit-body --only-merges --between-tags previous_version...next_version |
||||||
4) Commit new updated CHANGELOG.md |
- publish a release in github using the changelog |
||||||
|
- after remix_live is updated, drop the zip (from https://github.com/ethereum/remix-live/) to the release. |
||||||
|
|
||||||
|
## Remix-ide beta release |
||||||
|
- git fetch origin master |
||||||
|
- git checkout origin/master |
||||||
|
- git checkout -b bumpVersion |
||||||
|
- update package.json version to the new version "vx.x.x-beta.1" |
||||||
|
- remove package-lock/json version and generate a new one with `npm install` |
||||||
|
- merge PR |
||||||
|
- git fetch origin master |
||||||
|
- git checkout origin/master |
||||||
|
- git tag v(version-number) (with "vx.x.x-beta.1") |
||||||
|
- git push --tags |
||||||
|
- github-changes -o ethereum -r remix-ide -a --only-pulls --use-commit-body --only-merges --between-tags previous_version...next_version |
||||||
|
- publish a beta release in github using the changelog |
||||||
|
- drop zip file to the beta release (from https://github.com/ethereum/remix-live-alpha) |
||||||
|
|
||||||
|
## remix.ethereum.org update |
||||||
|
|
||||||
|
This is not strictly speaking a release. Updating the remix site is done through the Travis build: |
||||||
|
|
||||||
|
- git co -b remix_live origin/remix_live |
||||||
|
- git reset --hard -master-commit-hash- |
||||||
|
- git push -f origin remix_live |
||||||
|
|
||||||
|
CircleCI will build automaticaly and remix.ethereum.org will be updated |
||||||
|
|
||||||
|
## remix-alpha.ethereum.org update |
||||||
|
|
||||||
|
remix-alpha.ethereum.org is automaticaly updated every time commits are pushed to master |
||||||
|
|
||||||
|
Loading…
Reference in new issue