Difference between revisions of "VPP/CommitterTasks/CutRelease"
From fd.io
< VPP
| Line 1: | Line 1: | ||
| − | # Lay tag for “v16.09” on patch that is “last patch in series" (see [[VPP/Pushing_and_Testing_a_Tag| Pushing and Testing a Tag but note NO -rcX suffix!!!) | + | # Lay tag for “v16.09” on patch that is “last patch in series" (see [[VPP/Pushing_and_Testing_a_Tag| Pushing and Testing a Tag]] but note NO -rcX suffix!!!) |
# “remerge” patch on that commit - so it creates various artifacts. | # “remerge” patch on that commit - so it creates various artifacts. | ||
## Do remerge as per this [https://www.dropbox.com/s/3xs09a9lnliv1za/Screenshot%202016-09-07%2009.25.56.png?dl=0 picture] | ## Do remerge as per this [https://www.dropbox.com/s/3xs09a9lnliv1za/Screenshot%202016-09-07%2009.25.56.png?dl=0 picture] | ||
Revision as of 16:33, 7 September 2016
- Lay tag for “v16.09” on patch that is “last patch in series" (see Pushing and Testing a Tag but note NO -rcX suffix!!!)
- “remerge” patch on that commit - so it creates various artifacts.
- Do remerge as per this picture
- LF then downloads those DEB/RPMs and move to the RELEASE repo
- email helpdesk@fd.io with target time and schedule meeting
- Test install behaviour on currently supported platforms (ie Centos7.2, Ubuntu Trusty, Ubuntu Xenial)
- Install binary packages and verify VPP starts on supported VMs without any prior VPP installed
- Repeat above but upgrading from prior release of VPP to new release
- Contact csit-dev to ask how they want to test the new artifacts.
