...
| 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
Note: Ideally we should run this release in devnet for 24 hours to look at stability. In some cases, we've run dev in devnet before tagging the release. In other cases, we need to get a fix to the public testnet and just go ahead and upgrade. | 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 |
...