Difference between revisions of "VPP/CommitterTasks/FinalReleaseCandidate"

From fd.io
< VPP
Jump to: navigation, search
m (update example email links)
 
(One intermediate revision by one other user not shown)
Line 1: Line 1:
 
== VPP RC2 Milestone Tasklist ==
 
== VPP RC2 Milestone Tasklist ==
  
−
1. At least one week prior to RC2 Milestone, send an email reminder to vpp-dev@lists.fd.io. See [https://lists.fd.io/g/vpp-dev/message/7827 example email].
+
1. At least one week prior to RC2 Milestone (adjust accordingly if the RC1->RC2 interval is shorter than this), send an email reminder to vpp-dev@lists.fd.io. See [https://lists.fd.io/g/vpp-dev/message/7827 example email].
  
 
2. Resend the reminder a day or two before RC2.
 
2. Resend the reminder a day or two before RC2.
Line 8: Line 8:
  
 
4. Send an email to vpp-dev@lists.fd.io and csit-dev@lists.fdio announcing the completion of RC2.  See [https://lists.fd.io/g/vpp-dev/message/7861 example email].
 
4. Send an email to vpp-dev@lists.fd.io and csit-dev@lists.fdio announcing the completion of RC2.  See [https://lists.fd.io/g/vpp-dev/message/7861 example email].
−
:NOTE: The CSIT code freeze date typically co-incides with RC2.  At this point, they will pull their release throttle branch (e.g. rls1801) and add appropriate jenkins jobs (much like the VPP RC1 branch pull).
 
  
−
5. Keep an eye on the release throttle gerrit queue for a patch to start using the CSIT release branch.  Merge it when it has been verified.
+
5. Continue to watch/merge patches in the VPP release throttle branch.
−
:Examples:
+
−
::[https://gerrit.fd.io/r/#/q/project:vpp+AND+branch:stable/1801 VPP stable/1801 Gerrit Filter]
+
−
::VPP patch to use CSIT Release branch: https://gerrit.fd.io/r/#/c/10071/
+
−
 
+
−
6. Continue to watch/merge patches in the VPP release throttle branch.
+

Latest revision as of 18:27, 17 April 2019

VPP RC2 Milestone Tasklist

1. At least one week prior to RC2 Milestone (adjust accordingly if the RC1->RC2 interval is shorter than this), send an email reminder to vpp-dev@lists.fd.io. See example email.

2. Resend the reminder a day or two before RC2.

3. Lay down a tag (v18.01-rc2) on stable/1801 at HEAD.

4. Send an email to vpp-dev@lists.fd.io and csit-dev@lists.fdio announcing the completion of RC2. See example email.

5. Continue to watch/merge patches in the VPP release throttle branch.

Retrieved from "https://wiki.fd.io/index.php?title=VPP/CommitterTasks/FinalReleaseCandidate&oldid=9353"