Difference between revisions of "Projects/vpp/Release Plans/Release Plan 18.10"
From fd.io
(→Release Deliverables) |
|||
(14 intermediate revisions by 5 users not shown) | |||
Line 12: | Line 12: | ||
|- | |- | ||
| rowspan="1" | INFRA || DPDK 18.08 integration || | | rowspan="1" | INFRA || DPDK 18.08 integration || | ||
+ | |- | ||
+ | | rowspan="1" | LB || Support per-port VIP and all-port VIP || Done | ||
+ | |- | ||
+ | | rowspan="1" | NSH || Port NSH plugin to VPP || Done | ||
+ | |- | ||
+ | | rowspan="1" | MC-CRYPTO|| Support DPDK Multi-core Crypto-Dev ||In Progress: Review Id: 15084 | ||
+ | |- | ||
+ | | rowspan="2" | DPI|| Port Hyperscan to VPP || In progress | ||
+ | |- | ||
+ | || Support Block Mode and Single Pattern Match || In progress | ||
+ | |- | ||
+ | | rowspan="2" | INFRA || New Stats infrastructure (interface, error, node performance counters) || Done | ||
+ | |- | ||
+ | || Add configurable "Doug Lea malloc" support || Done | ||
+ | |- | ||
+ | | rowspan="5" | NAT || TCP MSS clamping || Done | ||
+ | |- | ||
+ | || Session timeout || Done | ||
+ | |- | ||
+ | || Configurable port range || Done | ||
+ | |- | ||
+ | || Virtual Fragmentation Reassembly for endpoint-dependent mode || Done | ||
+ | |- | ||
+ | || Client-IP based session affinity for load-balancing || Done | ||
|} | |} | ||
== Release Milestones == | == Release Milestones == | ||
− | <span style=" | + | <span style="font-size:120%">The schedule below is FINAL as agreed on Aug 21st during VPP project meeting</span> |
<!-- It is not uncommon for a project as part of its release process to have Milestones (M0, M1, M2, RC0, RC1) with corresponding events which occur at various milestones (API Freeze, Code Freeze, etc). This is the place to list Milestones, their expected dates, and their expected events (whether process events, API Freeze, or noting a deliverable is coming in at a particular event. --> | <!-- It is not uncommon for a project as part of its release process to have Milestones (M0, M1, M2, RC0, RC1) with corresponding events which occur at various milestones (API Freeze, Code Freeze, etc). This is the place to list Milestones, their expected dates, and their expected events (whether process events, API Freeze, or noting a deliverable is coming in at a particular event. --> | ||
Line 33: | Line 57: | ||
|- | |- | ||
| RC2 | | RC2 | ||
− | | 2018-10- | + | | 2018-10-17 (RC1 + 7) |
| Second artifacts posted. | | Second artifacts posted. | ||
|- | |- | ||
| Formal Release | | Formal Release | ||
− | | 2018-10- | + | | 2018-10-24 (RC2 + 7) |
| 18.10 release artifacts available | | 18.10 release artifacts available | ||
|} | |} |
Latest revision as of 07:39, 8 October 2018
Contents
[hide]Introduction
This page tracks release information for 18.10
Release Deliverables
Name | Description | Status |
---|---|---|
INFRA | DPDK 18.08 integration | |
LB | Support per-port VIP and all-port VIP | Done |
NSH | Port NSH plugin to VPP | Done |
MC-CRYPTO | Support DPDK Multi-core Crypto-Dev | In Progress: Review Id: 15084 |
DPI | Port Hyperscan to VPP | In progress |
Support Block Mode and Single Pattern Match | In progress | |
INFRA | New Stats infrastructure (interface, error, node performance counters) | Done |
Add configurable "Doug Lea malloc" support | Done | |
NAT | TCP MSS clamping | Done |
Session timeout | Done | |
Configurable port range | Done | |
Virtual Fragmentation Reassembly for endpoint-dependent mode | Done | |
Client-IP based session affinity for load-balancing | Done |
Release Milestones
The schedule below is FINAL as agreed on Aug 21st during VPP project meeting
Milestone | Date | Deliverables |
---|---|---|
F0 | 2018-10-03 | APIs frozen. Only low-risk changes accepted on main branch. |
RC1 | 2018-10-10 (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-10-17 (RC1 + 7) | Second artifacts posted. |
Formal Release | 2018-10-24 (RC2 + 7) | 18.10 release artifacts available |
NOTE: Dates chosen based on:
- end-month release
- milestone + days
- release date after VPP community meeting, for discussion, go/no-go
Once we've pulled the 18.10 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.10
NEED JIRA/CONFLUENCE IMPORT HERE