Release process

Releases

Versioning and tagging

The version of idchain-geth shall be the geth release version, prefixed with idc. Examples: idc1.9.15, idc1.9.15-u1-unstable. A git tag of this form will be created for each official release.

Upstream changes

When there is a new release tagged in a go-ethereum release branch, we may choose to

1. create a pull request to merge the geth release branch into the matching IDChain release branch. Example: https://github.com/BrightID/IDChain/pull/3 merges the branch release/1.9 of go-ethereum into release/1.9 of IDChain.
2. review and merge the pull request.
3. create a version tag matching the upstream version, so that it becomes an official IDChain release. Example: if geth has tagged the release v1.9.13, we will create a tag of the form idc1.9.13.

Our changes

When we make custom changes to our fork, we will

1. commit or merge them into the dev branch
2. create a pull request to merge them into the default branch for our repo (default branches have the form release/<version>).
3. create a version tag matching the upstream version, but with an update version (u-<number>) appended. Examples: idc1.9.13-u1, idc1.9.13-u2, etc.