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

From fd.io
Jump to: navigation, search
(Created page with " == Introduction == This page tracks release information for 17.10. == Release Deliverables == {|class="wikitable" ! Name ! Description |- |Infra |DPDK 17.08 integratio...")
 
(Release Deliverables)
Line 16: Line 16:
 
|Infra
 
|Infra
 
|DPDK 17.08 integration
 
|DPDK 17.08 integration
 +
|-
 +
|VNET
  
 +
|-
 +
|Host stack
 +
|VPP TCP stack - scale / congestion / API
 +
 +
|-
 +
|ONE-LISP
 +
|
 
|}
 
|}
  

Revision as of 16:18, 7 August 2017


Introduction

This page tracks release information for 17.10.


Release Deliverables

Name Description
Infra DPDK 17.08 integration
VNET
Host stack VPP TCP stack - scale / congestion / API
ONE-LISP

Release Milestones

Milestone Date Deliverables
F0 2017-09-07 APIs frozen. Only low-risk changes accepted on main branch.
RC1 2017-09-21 (F0+17) 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-05 (RC1+17) Second artifacts posted.
Formal Release 2017-10-19 (RC2+17) 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