Tasks to put into Jira for pre- and post-release work
Order of operation
...
- Code and documentation completeness in dev
- Cut and test packages and Docker image from dev
- Test installation documentation and tutorial
- Draft release announcement
...
- Deliver demo to Nash and Mike
- Merge to master
...
- Tag release
- Testing
- Update GitHub release page
- Update Docker hub
- Update dev web site with release-related content
...
- Deliver demo to RChain community
- Update release announcement with links
...
Purpose
The purpose of this page is to outline the work related to releasing new versions of RNode.
Process description
We release software at the end of each sprint, meaning we release whatever is in the dev branch at the end of the sprint.
| When | What | Responsible | Accountable | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| At the end of a sprint | Tag a release based on whatever is in the dev branch Example of a Jira ticket
| SRE team | PM | ||||||||
Update the public testnet Example of a Jira ticket
| SRE team | PM | |||||||||
Update the release page
Example of a release page RNode-0.9.10 release plan | PM | PM | |||||||||
Create the next release in Jira. | PM | PM | |||||||||
Create release plan for the next release. Hint: copy the current release plan and edit
| PM | PM | |||||||||
Update The Flight to Mercury
| PM | PM | |||||||||
| When all items above complete | Create a ticket for updating developer.rchain.coop page and assign to Derek Beres Example of a Jira ticket
| PM | PM | ||||||||
| Update developer.rchain.coop | Derek Beres | PM |