New platform version release process

Releasing a new main version (0.x.0)

1. Pull the latest from upstream/master

2. Create a new main version branch off master (i.e for new version 0.20 => git checkout -b v0.20)

3. Make sure you are logged in NPM public with the electrode-native NPM user account

4. Run node_modules/.bin/lerna publish --skip-git --exact
   When prompted to select a new version choose Minor and hit Enter. Confirm when prompted to proceed.

5. Update version in postinstall.js script
   For const PLATFORM_VERSION = replace with the right new version (i.e if 0.20.0 => const PLATFORM_VERSION = '0.20.0'

6. Git add all changes and push them to remote version branch
   i.e for version 0.20.0 => git add . / git commit -m "v0.20.0" / git push upstream v0.20

7. Git tag with current version
   i.e for version 0.20.0 => git tag v0.20.0

8. Push tag to upstream i.e for version 0.20.0 => git push upstream v0.20.0

9. Write release notes for new version tag in GitHub and publish the release notes Go through all PRs since previous released version

10. Slack all user channels to announce new version, linking release notes

Releasing a new patch version (0.x.y)

1. Checkout the main version branch
   i.e if you are planning to release 0.20.1 => git checkout 0.20

2. Make sure the version branch is in-sync with the remote
   i.e for 0.20 => git pull upstream 0.20

3. Cherry pick all commits from master that need to make it in this patch version

4. Make sure you are logged in NPM public with the electrode-native NPM user account

5. Run node_modules/.bin/lerna publish --skip-git --exact
   When prompted to select a new version choose Patch and hit Enter. Confirm when prompted to proceed.

6. Update version in postinstall.js script
   For const PLATFORM_VERSION = replace with the right new version (i.e if 0.20.1 => const PLATFORM_VERSION = '0.20.1'

7. Git add all changes and push them to remote version branch
   i.e for version 0.20.1 => git add . / git commit -m "v0.20.1" / git push upstream v0.20

8. Git tag with current version
   i.e for version 0.20.1 => git tag v0.20.1

9. Push tag to upstream i.e for version 0.20.1 => git push upstream v0.20.1

10. Write release notes for new version tag in GitHub and publish the release notes Go through all PRs since previous released version

11. Slack all user channels to announce new version, linking release notes