Release Process

Procedure to cut a Fabric release:

1. 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 [TBD].
2. Tag the master branch with the same name as the release branch
3. Publish release notes on Fabric Releases.
4. 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:

1. Select issues to fix for the release branch and label them as such with a label with a value of the release identifier.
2. Submit pull requests for those selected issues against the release branch.
3. Decide on whether to merge the changes from the release branch to the master branch or requesting the authors to submit the changes on both branches.
4. Maintainers resolve any merge conflicts.