Difference between revisions of "Projects/vpp/Release Plans/Release Plan 18.07"
From fd.io
(→Release Deliverables) |
Florin.coras (Talk | contribs) (→Release Deliverables) |
||
| Line 41: | Line 41: | ||
|| Integration of VCL & Envoy || | || Integration of VCL & Envoy || | ||
|- | |- | ||
| − | || | + | || Session: performance improvements, add support for connectionless transports, datagram reception and transmission || |
| + | |||
| + | || TCP: congestion control improvements and overall fixes || | ||
| + | |||
| + | || UDP: datagram mode || | ||
| + | |||
| + | || TLS async support || | ||
|- | |- | ||
Revision as of 15:49, 12 June 2018
Contents
Introduction
This page tracks release information for 18.04.
Release Deliverables
| Name | Description | Status | |||||
|---|---|---|---|---|---|---|---|
| INFRA | DPDK 18.05 integration | ||||||
| VNET | |||||||
| L2 performance Optimizations | |||||||
| Pollable Stats (VPP-55 ?) | |||||||
| IPSec (NAT traversal, TCP offload..) | |||||||
| DHCPv6 Prefix Delegation | |||||||
| HW offload (Vxlan, generic classifier) | |||||||
| AVF (for physical intel NICs) | |||||||
| VPP in Amazon with IPv6 | |||||||
| HOSTSTACK | |||||||
| Host stack/VCL performance tuning | |||||||
| Integration of VCL & Envoy | |||||||
| Session: performance improvements, add support for connectionless transports, datagram reception and transmission | TCP: congestion control improvements and overall fixes | UDP: datagram mode | TLS async support | ||||
| NAT | |||||||
| Code refactor | |||||||
| Syslog | |||||||
| Multiple outside interfaces | |||||||
| Endpoint dependent filtering and mapping | |||||||
| TCP MSS clamping | |||||||
| ACL | |||||||
| Tuple Merge algorithm cleanup and integration | |||||||
| Processing pipeline optimizations | |||||||
| Refactoring | |||||||
| LB | |||||||
| Refactor kube-proxy feature into LB plugin | |||||||
| Support stats for each vip and as |
Release Milestones
| Milestone | Date | Deliverables |
|---|---|---|
| F0 | 2018-07-09 | APIs frozen. Only low-risk changes accepted on main branch. |
| RC1 | 2018-07-16 (F0+7) | 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-07-23 (RC1+7) | Second artifacts posted. |
| Formal Release | 2018-07-30 (RC2+7) | 18.07 release 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.07 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 for commits into the stable branch and master.
Features to be added in 18.07
NEED JIRA/CONFLUENCE IMPORT HERE