Create a release branch, and name it vM.m[.p][-qualifier] where M is the major release identifier, m is minor release identifier, p is the patch level identifier (only for LTS releases) and -qualifier is from the taxonomy of release maturity labels. To create a new branch, navigate to https://gerrit.hyperledger.org/r/#/admin/projects/fabric,branches. You can replace 'fabric' in the URL with the project name.

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

Publish release notes in an update to fabric/docs/releases.md.

Announce the release, linking to the release notes on Hyperledger fabric and general slack channels and hyperledger-fabric and hyperledger-announce mailing lists