Difference between revisions of "VPP/CommitterTasks/CutRelease"

From fd.io
< VPP
Jump to: navigation, search
Line 1: Line 1:
 +
 +
= 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 [[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]
−
# LF then downloads those DEB/RPMs and move to the RELEASE repo
+
# Once remerge jobs have successfully completed open case with LF staff to move artifacts to release repo
−
## email helpdesk@fd.io with target time and schedule meeting
+
## 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).
−
# Test install behaviour on currently supported platforms (ie Centos7.2, Ubuntu Trusty, Ubuntu Xenial)
+
# 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
 
## 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
 
# Contact [mailto:csit-dev@lists.fd.io csit-dev] to ask how they want to test the new artifacts.
 
# Contact [mailto:csit-dev@lists.fd.io csit-dev] to ask how they want to test the new artifacts.
 +
 +
== helpdesk email template ==
 +
<pre>
 +
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 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 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 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
 +
 
 +
</pre>

Revision as of 21:20, 13 January 2017

Instructions for vpp release manager

  1. 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
  2. Lay tag for “v16.09” on patch that is “last patch in series" (see Pushing and Testing a Tag but note NO -rcX suffix!!!)
  3. “remerge” patch on that commit - so it creates various artifacts.
    1. Do remerge as per this picture
  4. Once remerge jobs have successfully completed open case with LF staff to move artifacts to release repo
    1. 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).
  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 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
    1. Install binary packages and verify VPP starts on supported VMs without any prior VPP installed
    2. Repeat above but upgrading from prior release of VPP to new release
  7. 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 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 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 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
Retrieved from "https://wiki.fd.io/index.php?title=VPP/CommitterTasks/CutRelease&oldid=4074"