projects:fabric:release-process
Procedure to cut a Fabric release
-
Create a Change Requests (CR) on the branch, labeled “Release xxx” and update Makefile:IS_RELEASE = true and Makefile:BASE_VERSION=xxx
Create another CR (basically “undo” the release state by the CR above), by setting Makefile:IS_RELEASE=false and Makefile:BASE_VERSION=xxx+1
Once accepted, submit a tag against the $sha of the first CR; the tag triggers Jenkins to build/publish the docker images. Here is an example of when we released v0.6.1-preview
CR1 and
CR2
-
Announce the release, linking to the release notes on Hyperledger fabric and general slack channels and hyperledger-fabric and hyperledger-announce mailing lists
Perform if necessary:
Select issues to fix for the release branch and label them as such with a label with a value of the release identifier.
Submit change requests for those selected issues against the release branch.
Maintainers decide on whether to merge the requested changes from the release branch to the master branch or requesting the authors to submit the changes on both branches.
projects/fabric/release-process.txt · Last modified: 2017/01/30 20:03 by Christopher Ferris