-
Notifications
You must be signed in to change notification settings - Fork 4
Release playbook
LAJ edited this page Jan 8, 2021
·
19 revisions
Rough notes for releasing programming model related Hyperledger Fabric projects
Need to think about/open Jira issues for:
- document release process in each repo (see below)
- https://jira.hyperledger.org/browse/FABCJ-290
- https://jira.hyperledger.org/browse/FABCN-422
- https://jira.hyperledger.org/browse/FABN-1591
- https://jira.hyperledger.org/browse/FABJ-522
- https://jira.hyperledger.org/browse/FABCAG-30
- https://jira.hyperledger.org/browse/FGJ-88
- Fabric Gateway Release process
- others? (chaincode/sdk Go?)
- decide when to release, e.g. should the trigger be
- a regular release schedule (assuming there is something to release)
- only to stay in sync with core Fabric
- based on the number/severity of commits since the last release
- do we prefer to checkpoint at the end of each sprint to see if we do or don’t want to push out a release? (Mark)
- vulnerability scans for each repo, i.e.
- required before each release
- could trigger a release
- Making improvements to release process
- automating post-release version bumps
- removing other manual steps?
Create a RELEASING.md file in each repo? i.e. similar to CONTRIBUTORS.md and CONTRIBUTING.md convention. Update CONTRIBUTING.md to explain branching model and link to the releasing guide.
- Fabric-Chaincode-Java Release Playbook
- Fabric-Chaincode-Node Release Process
- Java SDK Release Process Document
Jiras for previous releases for some background
- Chaincode/Contract go?
- Chaincode node
- Chaincode java
- Client SDK go?
- Client SDK node
- Client SDK java
Other resources which might be useful:
-
keep a changelog
- Don’t let your friends dump git logs into changelogs