Difference between revisions of "VPP/CommitterTasks/FinalReleaseCandidate"
From fd.io
< VPP
Dwallacelf (Talk | contribs) (→VPP RC2 Milestone Tasklist) |
m (update example email links) |
||
| 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 | + | 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]. |
2. Resend the reminder a day or two before RC2. | 2. Resend the reminder a day or two before RC2. | ||
| Line 7: | Line 7: | ||
3. [https://wiki.fd.io/view/VPP/Pushing_and_Testing_a_Tag Lay down a tag] (v18.01-rc2) on stable/1801 at HEAD. | 3. [https://wiki.fd.io/view/VPP/Pushing_and_Testing_a_Tag 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 | + | 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). | :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). | ||
Revision as of 18:45, 9 April 2018
VPP RC2 Milestone Tasklist
1. At least one week prior to RC2 Milestone, 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.
- 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.
- Examples:
- 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.
