Difference between revisions of "VPP/CommitterTasks/CutRelease"
From fd.io
< VPP
(→helpdesk email template) |
(→Instructions for vpp release manager) |
||
Line 8: | Line 8: | ||
## email helpdesk@fd.io using the email template below, substituting ${release number} with the release number (like 17.01) and ${release number without '.'} with the release number without '.' (like 1701). | ## email helpdesk@fd.io using the email template below, substituting ${release number} with the release number (like 17.01) and ${release number without '.'} with the release number without '.' (like 1701). | ||
# Wait for LF infra staff to indicate they have completed the case | # Wait for LF infra staff to indicate they have completed the case | ||
− | # Test install behaviour on currently supported platforms (ie Centos7.2, Ubuntu Trusty, Ubuntu Xenial) - use instructions for [[VPP/Installing_VPP_binaries_from_packages here]] to install 'release' packages and make sure you get a runnable version for ${release number} using release artifacts | + | # Test install behaviour on currently supported platforms (ie Centos7.2, Ubuntu Trusty, Ubuntu Xenial) - use instructions for [[VPP/Installing_VPP_binaries_from_packages| here]] to install 'release' packages and make sure you get a runnable version for ${release number} using release artifacts |
## Install binary packages and verify VPP starts on supported VMs without any prior VPP installed | ## 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 | ## Repeat above but upgrading from prior release of VPP to new release |
Revision as of 21:53, 16 January 2017
Instructions for vpp release manager
- It is strongly recommended you do this a day or two prior to release if you are relatively sure all needed code for the release is in
- 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
- Once remerge jobs have successfully completed open case with LF staff to move artifacts to release repo
- email helpdesk@fd.io using the email template below, substituting ${release number} with the release number (like 17.01) and ${release number without '.'} with the release number without '.' (like 1701).
- Wait for LF infra staff to indicate they have completed the case
- Test install behaviour on currently supported platforms (ie Centos7.2, Ubuntu Trusty, Ubuntu Xenial) - use instructions for here to install 'release' packages and make sure you get a runnable version for ${release number} using release artifacts
- 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.
helpdesk email template
Subject: Publish vpp release artifacts vpp has completed release ${release number}. Please copy: https://nexus.fd.io/content/repositories/fd.io.stable.${release number without '.'}.centos7/io/fd/vpp/*/${release number}-release.x86_64/*.rpm to https://nexus.fd.io/content/repositories/fd.io.centos7/io/fd/vpp/*/${release number}-release.x86_64/*.rpm Please note: the groupId will be io.fd.vpp, the maven version will be ${release_number}-release.x86_64, the artifactId will be the '*' between io/fd/vpp/ and ${release_number}-release.x86_64 Please copy: https://nexus.fd.io/content/repositories/fd.io.stable.${release number}.ubuntu.trusty.main/io/fd/vpp/*/${release number}_amd64/*.deb to https://nexus.fd.io/content/repositories/fd.io.ubuntu.trusty.main/io/fd/vpp/*/${release number}_amd64/*.deb Please note: the groupId will be io.fd.vpp, the maven version will be ${release_number}_amd64, the artifactId will be the '*' between io/fd/vpp/ and ${release number}_amd64 Please copy: https://nexus.fd.io/content/repositories/fd.io.stable.${release number}.ubuntu.xenial.main/io/fd/vpp/*/${release number}_amd64/*.deb to https://nexus.fd.io/content/repositories/fd.io.ubuntu.xenial.main/io/fd/vpp/*/${release number}_amd64/*.deb Please note: the groupId will be io.fd.vpp, the maven version will be ${release_number}_amd64, the artifactId will be the '*' between io/fd/vpp/ and ${release number}_amd64 Please copy https://nexus.fd.io/content/repositories/fd.io.snapshot/io/fd/vpp/*/${release number}-SNAPSHOT/*.jar where you select the jar file with the highest build number to https://nexus.fd.io/content/repositories/fd.io.release/io/fd/vpp/*/${release number}/*.jar Please note: the groupId will be io.fd.vpp, the maven version will be ${release_number}, the artifactId will be the '*' between io/fd/vpp/ and ${release number} When performing all of these copies, please make sure to *not* copy the .pom files.