VPP Release_Plans Release_Plan_17.10

Contents

• 1 Introduction
• 2 Release Deliverables
• 3 Release Milestones
• 4 Once we've pulled the 17.10 release throttle
  • 4.1 Features to be added in 17.10
• 5 Expected Dependencies on Other Projects

Introduction

This page tracks release information for 17.10.

Release Deliverables

Name	Description
Infra	DPDK 17.08 integration IP reassembly
VNET	IPSec rework - utilize new FIB VPLS and VPWS implementation
SNAT / NAT	Complete NAT64 Performance / Scale Fragmentation support One-armed NAT (internal and external on same interface) Syslog support
API	C/C++ language binding API stats
Security Groups / ACL	Subinterface / tagged interface test suite and official support "replace" semantics for adding a new MacIP acl Test suite tests for MacIP ACLs
Host stack	VPP TCP stack - scale / congestion VPP Comms Library (VLC)
ONE-LISP	Default route overwriting Map-server fallback support Preemptive re-fetch of active mappings that are about to expire Separate control plane protocol from logic ND termination Separate configuration for xTR/PITR/PETR functions
PPPoE	PPPoE Control Plane packet dispatch PPPoE decapsulation PPPoE encapsulation

Release Milestones

Milestone	Date	Deliverables
F0	2017-09-13	APIs frozen. Only low-risk changes accepted on main branch.
RC1	2017-09-27 (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-10-11 (RC1+14)	Second artifacts posted.
Formal Release	2017-10-25 (RC2+14)	17.10 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.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

Features to be added in 17.10

NEED JIRA/CONFLUENCE IMPORT HERE

Expected Dependencies on Other Projects