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 - RCHAIN-3597Getting issue details... STATUS | SRE team | PM |
Update the public testnet Example of a Jira ticket - RCHAIN-3596Getting issue details... STATUS | 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 | PM | PM | |
Update developer.rchain.coop | Derek Beres | PM |