Difference between revisions of "VPP/CommitterTasks/CutRelease"
Dwallacelf (Talk | contribs) (→Recipe to Generate the Release) |
Dwallacelf (Talk | contribs) (→Recipe to Generate the Release) |
||
| (6 intermediate revisions by 2 users not shown) | |||
| Line 11: | Line 11: | ||
2. Review docs.fd.io | 2. Review docs.fd.io | ||
:a. On the release throttle branch (e.g. stable/1801), add release specific links to .../vpp/doxygen/test_framework_doc.md | :a. On the release throttle branch (e.g. stable/1801), add release specific links to .../vpp/doxygen/test_framework_doc.md | ||
| − | :b. From workspace root, build doxygen output | + | :b. <b>pre-22.02</b> From workspace root, build doxygen output |
::<pre>make bootstrap-doxygen doxygen</pre> | ::<pre>make bootstrap-doxygen doxygen</pre> | ||
| + | :b. <b>post-22.02</b> From workspace root, build docs | ||
| + | ::<pre>make docs</pre> | ||
:c. Check documentation output by opening the document index file in a browser: | :c. Check documentation output by opening the document index file in a browser: | ||
::file:///<path to workspace root>/build-root/docs/html/index.html | ::file:///<path to workspace root>/build-root/docs/html/index.html | ||
| Line 38: | Line 40: | ||
9. Cherry-pick release notes patch to master. | 9. Cherry-pick release notes patch to master. | ||
| + | |||
| + | 10. Review patches to the previous stable/XXXX release branch to ensure that all bug fixes in the previous release | ||
| + | are contained in the new release. | ||
== Recipe to Generate the Release == | == Recipe to Generate the Release == | ||
| − | WARNING: If you push the release tag before the merge jobs have completed from the release note patch, then the merge jobs will fail when you do the "remerge" step below because nexus does not allow overwriting artifacts that already exist. If this does happen, then you need to open a | + | WARNING: If you push the release tag before the merge jobs have completed from the release note patch, then the merge jobs will fail when you do the "remerge" step below because nexus does not allow overwriting artifacts that already exist. If this does happen, then you need to open a [https://support.linuxfoundation.org helpdesk ticket] asking for all of the nexus release artifacts to be purged. You can also encounter this issue if the "remerge" jobs fail (keep your fingers crossed ;) |
1. Send an email reminder to the VPP Committers to NOT MERGE ANY PATCHES onto the stable branch until after the completion of the release has been announced on vpp-dev@lists.fd.io. | 1. Send an email reminder to the VPP Committers to NOT MERGE ANY PATCHES onto the stable branch until after the completion of the release has been announced on vpp-dev@lists.fd.io. | ||
2. Lay tag for “v18.01” on patch that is “last patch in series" (see [[VPP/Pushing_and_Testing_a_Tag| Pushing and Testing a Tag]] but note '''NO -rc<#>''' suffix!!!) | 2. Lay tag for “v18.01” on patch that is “last patch in series" (see [[VPP/Pushing_and_Testing_a_Tag| Pushing and Testing a Tag]] but note '''NO -rc<#>''' suffix!!!) | ||
| + | |||
| + | 2a. IMPORTANT: verify in https://git.fd.io/vpp/ that the tag has been propagated and is visible. It sometimes takes a while. If the correct tag is not there at the time of the merge job start, the artifact labelling will be wrong. | ||
3. “remerge” patch on that commit - so it creates various artifacts. | 3. “remerge” patch on that commit - so it creates various artifacts. | ||
| Line 50: | Line 57: | ||
4. Once remerge jobs have successfully completed open case with LF staff to move artifacts to release repo | 4. Once remerge jobs have successfully completed open case with LF staff to move artifacts to release repo | ||
| − | :* | + | :* Open a [https://support.linuxfoundation.org helpdesk ticket] using the template below, substituting ${release number} with the release number (like 18.01) and ${release number without '.'} with the release number without '.' (like 1801). |
5. Wait for LF infra staff to indicate they have completed the case | 5. Wait for LF infra staff to indicate they have completed the case | ||
| Line 72: | Line 79: | ||
:* Email [mailto:vpp-dev@lists.fd.io vpp-dev] and [mailto:csit-dev@lists.fd.io csit-dev] to announce the availability of the release artifacts on nexus.fd.io. | :* Email [mailto:vpp-dev@lists.fd.io vpp-dev] and [mailto:csit-dev@lists.fd.io csit-dev] to announce the availability of the release artifacts on nexus.fd.io. | ||
| − | == helpdesk | + | == helpdesk template == |
<pre> | <pre> | ||
Subject: Please publish VPP ${release number} Release Artifacts | Subject: Please publish VPP ${release number} Release Artifacts | ||
| Line 78: | Line 85: | ||
Dear Helpdesk@fd.io, | Dear Helpdesk@fd.io, | ||
| − | The VPP artifacts for release ${release number} are now available on packagecloud | + | The VPP artifacts for release ${release number} are now available on packagecloud.io and are ready to be copied into the release directories. |
| − | Please let me know when they have been published so I can test the VPP ${release number} | + | Please let me know when they have been published so I can test the VPP ${release number} packages from packagecloud.io/fdio/release. |
Thanks, | Thanks, | ||
| Line 88: | Line 95: | ||
== Post Release Tasks == | == Post Release Tasks == | ||
| − | 1. | + | 1. Rebuild the docs |
| − | + | make docs-venv docs | |
| + | |||
| + | 2. Submit the patch containing the updated docs about release version file .../docs/about.rst | ||
| + | * For example, [https://gerrit.fd.io/r/c/vpp/+/23047 VPP 19.04.3 docs build info] | ||
| − | + | 3. Create the tag for the next maintenance release “v19.04.4-rc0” on the patch (see [[VPP/Pushing_and_Testing_a_Tag| Pushing and Testing a Tag]]). | |
| − | + | This tag is required to ensure that the latest artifacts pushed to packagecloud.io/1904 get retrieved when pulling from the repo using apt or yum. | |
| − | + | ||
| − | + | 4. Merge the patch [Verified +1, Code Review +2] | |
Latest revision as of 15:58, 30 October 2024
Contents
Instructions for vpp release manager
It is strongly recommended you do the prerequisites the week prior to the FR Milestone and start the release process a day or two prior to release.
Prerequisites
1. Update Wiki - Edit the following wiki pages and add/revise references for new release
2. Review docs.fd.io
- a. On the release throttle branch (e.g. stable/1801), add release specific links to .../vpp/doxygen/test_framework_doc.md
- b. pre-22.02 From workspace root, build doxygen output
make bootstrap-doxygen doxygen
- b. post-22.02 From workspace root, build docs
make docs
- c. Check documentation output by opening the document index file in a browser:
- file:///<path to workspace root>/build-root/docs/html/index.html
- d. Clean up any formatting issues found.
- e. Submit patch.
- f. After patch is merged, cherry-pick it to master.
3. Update .../vpp/extras/scripts/list_api_changes.py with current release rc0 tag (if necessary)
4. Update release notes
- a. Edit .../vpp/RELEASE.md and add section for the current release
- b. Add number of commits by running the following command on the throttle branch (e.g. 18.01 <release rc0 tag> == v18.01-rc0)
git rev-list <release rc0 tag>..HEAD | wc -l
- c. Add Features section from the Release Plan & git log (Hint: gitk is your friend, jira not so much)
- d. Add list of API changes generated using VPP
- e. Add list of patches that changed api files by running the updated list_api_changes.py script
5. Submit release notes patch (e.g. "18.01 Release Notes")
6. Send email to vpp-dev@lists.fd.io asking for feedback on the release notes patch.
7. Merge release notes patch (which should be the patch where the release label is created).
8. Verify that all merge jobs (including docs) have completed successfully.
9. Cherry-pick release notes patch to master.
10. Review patches to the previous stable/XXXX release branch to ensure that all bug fixes in the previous release are contained in the new release.
Recipe to Generate the Release
WARNING: If you push the release tag before the merge jobs have completed from the release note patch, then the merge jobs will fail when you do the "remerge" step below because nexus does not allow overwriting artifacts that already exist. If this does happen, then you need to open a helpdesk ticket asking for all of the nexus release artifacts to be purged. You can also encounter this issue if the "remerge" jobs fail (keep your fingers crossed ;)
1. Send an email reminder to the VPP Committers to NOT MERGE ANY PATCHES onto the stable branch until after the completion of the release has been announced on vpp-dev@lists.fd.io.
2. Lay tag for “v18.01” on patch that is “last patch in series" (see Pushing and Testing a Tag but note NO -rc<#> suffix!!!)
2a. IMPORTANT: verify in https://git.fd.io/vpp/ that the tag has been propagated and is visible. It sometimes takes a while. If the correct tag is not there at the time of the merge job start, the artifact labelling will be wrong.
3. “remerge” patch on that commit - so it creates various artifacts.
- Do remerge as per this picture
4. Once remerge jobs have successfully completed open case with LF staff to move artifacts to release repo
- Open a helpdesk ticket using the template below, substituting ${release number} with the release number (like 18.01) and ${release number without '.'} with the release number without '.' (like 1801).
5. Wait for LF infra staff to indicate they have completed the case
6. Test install behaviour on currently supported platforms (ie Centos7.2, Ubuntu Xenial) - use instructions for here to install 'release' packages and make sure you get a runnable version for ${release number} using release artifacts
- a. Review the packages on PackageCloud.io (change release number in the search bar as necessary):
- b. Install binary packages and verify VPP starts on supported VMs without any prior VPP installed
7. Release the version in Jira
VPP committers should have admin access to Jira. From https://jira.fd.io/plugins/servlet/project-config/VPP/summary navigate to Releases (Or Versions, same thing) and under Actions for the release, select Release.
Tell Jira to move all still-open issues into the next release and set the release date appropriately.
8. Declare Victory!
helpdesk template
Subject: Please publish VPP ${release number} Release Artifacts
Dear Helpdesk@fd.io,
The VPP artifacts for release ${release number} are now available on packagecloud.io and are ready to be copied into the release directories.
Please let me know when they have been published so I can test the VPP ${release number} packages from packagecloud.io/fdio/release.
Thanks,
<Your Friendly VPP Release Manager>
Post Release Tasks
1. Rebuild the docs
make docs-venv docs
2. Submit the patch containing the updated docs about release version file .../docs/about.rst
- For example, VPP 19.04.3 docs build info
3. Create the tag for the next maintenance release “v19.04.4-rc0” on the patch (see Pushing and Testing a Tag). This tag is required to ensure that the latest artifacts pushed to packagecloud.io/1904 get retrieved when pulling from the repo using apt or yum.
4. Merge the patch [Verified +1, Code Review +2]
