Release process

This document includes:

RemixD release

git fetch origin remix_beta
git checkout origin/remix_beta
git checkout -b bumpVersion
update package.json version
remove package-lock.json version and generate a new one with npm install
merge PR to origin/remix_beta
git fetch origin remix_beta
git checkout origin/remix_beta
git tag v(version-number)
git push --tags
github-changes -o ethereum -r remix-project -a --only-pulls --use-commit-body --branch remix_beta --only-merges --between-tags previous_version...next_version
publish a release in github using the changelog

git fetch origin master
git checkout origin/master
git checkout -b bumpDevVersion
update package.json version: bump the version and add the tag dev if not already present.
remove package-lock.json version and generate a new one with npm install
create a PR and merge it to origin/master

This is not strictly speaking a release. Updating the remix site is done through the Travis build:

CircleCI will build automaticaly and remix.ethereum.org will be updated

after remix_live is updated, drop the zip (from https://github.com/ethereum/remix-live/) to the 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-project -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-alpha.ethereum.org is automaticaly updated every time commits are pushed to master