Difference between revisions of "Projects/vpp/Release Plans/Release Plan 17.04"

From fd.io
Jump to: navigation, search
(Release Deliverables)
Line 13: Line 13:
 
|-
 
|-
 
|Infra
 
|Infra
|DPDK 17.03, DPDK in a separate shared library, Retirement of VPP_Lite, Lazy Polling mode
+
|DPDK 17.03
 +
 
 +
DPDK in a separate shared library
 +
 
 +
Retirement of VPP_Lite
 +
 
 +
Lazy Polling mode
 +
 
 +
Test infrastructure - multi-thread support
 
|-
 
|-
|SNAT improvements
+
|SNAT
|CGN (configurable port allocation, address pooling), CPE NAT44 features
+
|CGN: Configurable port allocation  
 +
 
 +
CGN: Configurable Address pooling
 +
 
 +
CPE: External interface DHCP support
 +
 
 +
NAT64, LW46
 +
 
 +
|-
 +
|Security Groups
 +
|Routed interface support
 +
 
 +
L4 filters with IPv6 Extension Headers
 +
 
 +
|-
 +
|API
 +
| Move to CFFI for Python binding
 +
 
 +
Python Packaging improvements
 +
 
 +
CLI over API
 +
 
 +
C/C++ language binding
 
|-
 
|-
 
|}
 
|}

Revision as of 12:05, 31 January 2017

Introduction

Release Deliverables

Name Description
IP multicast
Infra DPDK 17.03

DPDK in a separate shared library

Retirement of VPP_Lite

Lazy Polling mode

Test infrastructure - multi-thread support

SNAT CGN: Configurable port allocation

CGN: Configurable Address pooling

CPE: External interface DHCP support

NAT64, LW46

Security Groups Routed interface support

L4 filters with IPv6 Extension Headers

API Move to CFFI for Python binding

Python Packaging improvements

CLI over API

C/C++ language binding

Release Milestones

Milestone Date Deliverables
F0 2017-03-08 APIs frozen. Only low-risk changes accepted on main branch.
RC1 2017-03-22 (F0+14) 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 2017-04-05 (RC1+14) Second artifacts posted.
Formal Release 2017-04-19 (RC2+14) 17.04 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 17.04 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 17.07

This list generated using JIRA search:vpp issues:features/tasks release:1609

NEED JIRA/CONFLUENCE IMPORT HERE

Expected Dependencies on Other Projects