You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 5
Next »
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-3597
-
Getting issue details...
STATUS
| SRE team | PM |
| Update the public testnet Example of a Jira ticket
RCHAIN-3596
-
Getting issue details...
STATUS
| SRE team | PM |
| Update the release page - Update page header information
- Confirm work shown as included in the release is correct
- Write plain English description of the highlights of the release
- What makes this release good?
- Call out breaking changes
- Call out changes impacting node operators and/or dapp developers
Example of a release page RNode-0.9.10 release plan | PM | PM |
| Create the next release in Jira. https://rchain.atlassian.net/projects/RCHAIN?selectedItem=com.atlassian.jira.jira-projects-plugin%3Arelease-page | PM | PM |
| Create release plan for the next release. Hint: copy the current release plan and edit | PM | PM |
| Update The Flight to Mercury - Update listing for current release
- Create new listing for next release
| 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
WEB-160
-
Getting issue details...
STATUS
. Note this is in the Web project in Jira and not RChain project. | PM | PM |
| Update developer.rchain.coop | Derek Beres | PM |