Difference between revisions of "VPP/CommitterTasks/ApiFreeze"
From fd.io
< VPP
Dwallacelf (Talk | contribs) (→VPP F0 Milestone - API Freeze) |
Dwallacelf (Talk | contribs) |
||
| Line 2: | Line 2: | ||
== VPP F0 Milestone API Freeze Tasklist == | == VPP F0 Milestone API Freeze Tasklist == | ||
# Announce the VPP F0 Milestone date at the two meetings prior to the API Freeze date, requesting that contributors inform you of pending api changes and to update the Release Deliverables section of the Release Plan. | # Announce the VPP F0 Milestone date at the two meetings prior to the API Freeze date, requesting that contributors inform you of pending api changes and to update the Release Deliverables section of the Release Plan. | ||
| − | # Track patches with api changes using this [https://gerrit.fd.io/r/#/q/project:vpp+is:open+file:^.*\.api | + | # Track patches with api changes using this [https://gerrit.fd.io/r/#/q/project:vpp+is:open+file:^.*\.api Gerrit URL.] |
# At least a week prior to the F0 Milestone, send an email to vpp-dev@lists.fd.io announcing the F0 Milestone including a list the open patches with API files. See [https://lists.fd.io/pipermail/vpp-dev/2017-December/007686.html example email.] | # At least a week prior to the F0 Milestone, send an email to vpp-dev@lists.fd.io announcing the F0 Milestone including a list the open patches with API files. See [https://lists.fd.io/pipermail/vpp-dev/2017-December/007686.html example email.] | ||
# Work with VPP committers to ensure that patches intended for the release are reviewed/merged. | # Work with VPP committers to ensure that patches intended for the release are reviewed/merged. | ||
# Send a reminder email a couple of days prior to the F0 date and again on F0 day. | # Send a reminder email a couple of days prior to the F0 date and again on F0 day. | ||
Revision as of 22:03, 5 February 2018
VPP F0 Milestone API Freeze Tasklist
- Announce the VPP F0 Milestone date at the two meetings prior to the API Freeze date, requesting that contributors inform you of pending api changes and to update the Release Deliverables section of the Release Plan.
- Track patches with api changes using this Gerrit URL.
- At least a week prior to the F0 Milestone, send an email to vpp-dev@lists.fd.io announcing the F0 Milestone including a list the open patches with API files. See example email.
- Work with VPP committers to ensure that patches intended for the release are reviewed/merged.
- Send a reminder email a couple of days prior to the F0 date and again on F0 day.
