blob: a46d3856e8b1be318b25e6d93b26a8b94c8db7e3 [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 Armstrongbd6cc3d2023-01-09 19:52:12 -05008- Create a new dashboard for the future release candidate.
Joey Armstrong2ce92d02023-06-03 18:54:56 -04009- Visit the current released candidate version and move all unresolved tickets into the future desktop.
Joey Armstrongbd6cc3d2023-01-09 19:52:12 -050010- On release day click the [Release] button to close out the desktop.
Joey Armstrong2ce92d02023-06-03 18:54:56 -040011
12Confluence
13----------
14Create a `release tracking page` <https://wiki.opennetworking.org/display/VOLTHA/v2.12>`_ in confluence, there are a lot of details
15
16- Jira tickets related to release and VOLTHA builds.
17- Jenkins jobs: state, failures and tickets.
18- Versions and build state of dependent apps and packages (also merged into release notes).
19
20docs.voltha.org
21---------------
22- 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 -040023
24golang repositories
25-------------------
26
27- Upgrade go.mod (voltha-proto version at a minimum) early.
28- Force a build to triage potential problems.
29- Another go.mod update will be needed after voltha-protos
30 is published but screen early for a set of known problems.