blob: c92210647c05cfbbe13abc880624f666d431e55c [file] [log] [blame]
Joey Armstrongbd6cc3d2023-01-09 19:52:12 -05001Release Preparation
2===================
3
Joey Armstrong2ce92d02023-06-03 18:54:56 -04004Jira Tickets
5------------
6As release date approaches and development slows visit the `jira versions dashboard <https://jira.opencord.org/projects/VOL?selectedItem=com.atlassian.jira.jira-projects-plugin%3Arelease-page&status=unreleased>`_.
7
Joey Armstrong34f18402023-07-21 18:58:10 -04008- Create a new/empty dashboard for the future release candidate.
9
10 - Click in the ``Version name`` box and type in VOLTHA-(X.Y)++ for the next release.
11 - Enter start/end dates if known, they should overlap with the last release.
12
Joey Armstrong2ce92d02023-06-03 18:54:56 -040013- Visit the current released candidate version and move all unresolved tickets into the future desktop.
Joey Armstrong34f18402023-07-21 18:58:10 -040014
15 - TSTs may want to review unresolved tickets for release notes content for partially completed work.
16
Joey Armstrongbd6cc3d2023-01-09 19:52:12 -050017- On release day click the [Release] button to close out the desktop.
Joey Armstrong2ce92d02023-06-03 18:54:56 -040018
19Confluence
20----------
Joey Armstrong1b8fdc32023-12-20 17:22:57 -050021Create a `release tracking page <https://wiki.opencord.org>`_ in confluence, there are a lot of details
Joey Armstrong2ce92d02023-06-03 18:54:56 -040022
23- Jira tickets related to release and VOLTHA builds.
24- Jenkins jobs: state, failures and tickets.
25- Versions and build state of dependent apps and packages (also merged into release notes).
26
27docs.voltha.org
28---------------
Joey Armstrong45fe8052023-06-23 09:51:02 -040029- Create a stub `release notes <https://docs.voltha.org/master/release_notes/voltha_2.12.html>`_ page beneath `docs.voltha.org/release_notes <https://docs.voltha.org/master/release_notes/index.html>`_ (`HOWTO <https://docs.voltha.org/master/howto/release/release-notes.html>`_)
Joey Armstrongab04e262023-06-13 14:32:35 -040030
31golang repositories
32-------------------
33
34- Upgrade go.mod (voltha-proto version at a minimum) early.
35- Force a build to triage potential problems.
36- Another go.mod update will be needed after voltha-protos
37 is published but screen early for a set of known problems.