Difference between revisions of "VPP/CommitterTasks/CutPointRelease"

From fd.io
< VPP
Jump to: navigation, search
(Created page with "== VPP Point Release Tasklist == 1. Update Release Notes :a. Edit .../vpp/RELEASE.md and add section for the point release ::[https://docs.fd.io/vpp/18.01/release_notes_17011...")
 
Line 2: Line 2:
  
 
1. Update Release Notes
 
1. Update Release Notes
:a. Edit .../vpp/RELEASE.md and add section for the point release
+
:a. On the release throttle branch (e.g. stable/1801), edit .../vpp/RELEASE.md and add section for the point release
 
::[https://docs.fd.io/vpp/18.01/release_notes_17011.html Bug fix release note]
 
::[https://docs.fd.io/vpp/18.01/release_notes_17011.html Bug fix release note]
 
::TBD-link to 1801.1 release notes diff  
 
::TBD-link to 1801.1 release notes diff  
:b. Submit patch to release throttle branch (e.g. stable/1801)
+
:b. From workspace root, build doxygen output
:c. Verify generated docs, then merge patch.
+
::<pre>make bootstrap-doxygen doxygen</pre>
:d. Cherry-pick the release notes patch to master.
+
: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.
  
2. Follow the [[VPP/CommitterTasks/CutRelease#Recipe_to_Generate_the_Release | recipe to generate the release]] using the point release number (e.g. s/18.01/18.01.1/g and s/18011/1801/g).
+
2. Update the package version used by java generation on master with the point release version in .../vpp/src/configure.ac
 +
:a. On the throttle branch (e.g. stable/1801), edit .../vpp/src/configure.ac
 +
::TBD-link to 1801.1 configure.ac patch.
 +
:b. Submit patch. '''DO NOT CHERRY PICK THIS PATCH TO MASTER!'''
 +
:c. Merge patch and wait for merge jobs to complete prior to moving on to step 3.
 +
 
 +
3. Follow the [[VPP/CommitterTasks/CutRelease#Recipe_to_Generate_the_Release | recipe to generate the release]] using the point release number (e.g. s/18.01/18.01.1/g and s/18011/1801/g).

Revision as of 01:45, 7 February 2018

VPP Point Release Tasklist

1. Update Release Notes

a. On the release throttle branch (e.g. stable/1801), edit .../vpp/RELEASE.md and add section for the point release
Bug fix release note
TBD-link to 1801.1 release notes diff
b. From workspace root, build doxygen output
make bootstrap-doxygen doxygen
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.

2. Update the package version used by java generation on master with the point release version in .../vpp/src/configure.ac

a. On the throttle branch (e.g. stable/1801), edit .../vpp/src/configure.ac
TBD-link to 1801.1 configure.ac patch.
b. Submit patch. DO NOT CHERRY PICK THIS PATCH TO MASTER!
c. Merge patch and wait for merge jobs to complete prior to moving on to step 3.

3. Follow the recipe to generate the release using the point release number (e.g. s/18.01/18.01.1/g and s/18011/1801/g).