Projects/vpp/Release Plans/Release Plan 18.01
From fd.io
Revision as of 17:48, 12 December 2017 by Dwallacelf (Talk | contribs)
Contents
Introduction
This page tracks release information for 18.01.
Release Deliverables
| Name | Description |
|---|---|
| Infra | DPDK 17.11 integration
IP Reassembly TCP Checksum Offload |
| VNET | TBD |
| SNAT / NAT | One armed NAT
NAT64: multi thread Twice NAT Fragmentation / Reassembly Syslog |
| API | VPP stats (Broadcast & Multicast support)
VPP per node stats (show run equivalent) |
| Host stack | VPP TCP stack - scale / congestion
VPP Comms Library (VCL) |
| ACL | hash-acl lookup enhancement
ACL stats |
Release Milestones
| Milestone | Date | Deliverables |
|---|---|---|
| F0 | 2017-12-20 | APIs frozen. Only low-risk changes accepted on main branch. |
| RC1 | 2018-01-03 | Code complete, pull first release throttle branch, only bug fixes accepted on throttle train. After pull: main branch reopens for new feature / risky commits. First artifacts posted. |
| RC2 | 2018-01-10 | Second artifacts posted. |
| Formal Release | 2018-01-24 | 18.01 artifacts available |
NOTE: Dates chosen based on:
- mid-month release
- milestone + days
- day after VPP community meeting, for discussion, go/no-go
Once we've pulled the 18.01 release throttle
We need to be disciplined with respect to bugfix commits. Here are a few common-sense suggestions:
- All bug fixes must be double-committed to the release throttle as well as to the master branch
- Commit first to the release throttle, then "git cherry-pick" into master
- Manual merges may be required, depending on the degree of divergence between throttle and master
- All bug fixes need to have a Jira ticket
- Please put Jira IDs into the commit messages.
- Please use the same Jira ID
Features to be added in 18.01
NEED JIRA/CONFLUENCE IMPORT HERE
