Release Preparation¶
Jira Tickets¶
As release date approaches and development slows visit the jira versions dashboard.
Create a new/empty dashboard for the future release candidate.
Click in the
Version name
box and type in VOLTHA-(X.Y)++ for the next release.Enter start/end dates if known, they should overlap with the last release.
Visit the current released candidate version and move all unresolved tickets into the future desktop.
TSTs may want to review unresolved tickets for release notes content for partially completed work.
On release day click the [Release] button to close out the desktop.
Confluence¶
Create a release tracking page in confluence, there are a lot of details
Jira tickets related to release and VOLTHA builds.
Jenkins jobs: state, failures and tickets.
Versions and build state of dependent apps and packages (also merged into release notes).
docs.voltha.org¶
Create a stub release notes page beneath docs.voltha.org/release_notes (HOWTO)
golang repositories¶
Upgrade go.mod (voltha-proto version at a minimum) early.
Force a build to triage potential problems.
Another go.mod update will be needed after voltha-protos is published but screen early for a set of known problems.