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

From fd.io
Jump to: navigation, search
(Blanked the page)
 
Line 1: Line 1:
[[Category:Release Plan]]
 
== Introduction ==
 
  
== Release Deliverables ==
 
 
 
{|class="wikitable"
 
! Name
 
! Description
 
|-
 
| dpdk-16.11
 
| Support for the November 2016 dpdk release
 
|-
 
| FIB 2.0
 
| Enhanced FIB
 
|-
 
| dpdk CryptoDev
 
| Enable IPSec code to use DPDK CryptoDev (both sw and hw crypto). Adds Support for Intel QAT.
 
|-
 
| NAT Improvements
 
|
 
|-
 
| LLDP
 
| Implementation of Link Layer Discovery Protocol
 
|-
 
| IPFIX
 
| IPFIX Enhancements
 
|-
 
| DoxyGen
 
|
 
|-
 
| Unit Test
 
| Infrastructure (Python + Scapy based)
 
|-
 
| L2 Classifier
 
| Improvements
 
|}
 
 
== Release Milestones ==
 
 
<!-- 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. -->
 
 
{| class="wikitable"
 
! Milestone
 
! Date
 
! Deliverables
 
|-
 
| F0
 
| 2016-12-07
 
| APIs frozen. Only low-risk changes accepted on main branch.
 
|-
 
| RC1
 
| 2016-12-21 (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-01-04 (RC1+14)
 
| Second artifacts posted.
 
|-
 
| Formal Release
 
| 2017-01-18 (RC2+14)
 
| 17.01 artifacts available
 
|}
 
 
<span style="color:#ff0000; font-size:75%">''NOTE: Dates chosen based on:''</span>
 
* <span style="color:#ff0000; font-size:75%">''mid-month release''</span>
 
* <span style="color:#ff0000; font-size:75%">''milestone + days''</span>
 
* <span style="color:#ff0000; font-size:75%">''day after VPP community meeting, for discussion, go/no-go''</span>
 
 
== Once we've pulled the 17.01 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.01 ===
 
This list generated using JIRA search:[https://jira.fd.io/issues/?filter=10403 vpp issues:features/tasks release:1609]
 
 
<span style="color:#ff0000; font-size:100%"><div style="text-align:center">NEED JIRA/CONFLUENCE IMPORT HERE</div></span>
 
 
== Expected Dependencies on Other Projects ==
 
 
<!-- If your project depends on other projects, and particularly specific deliverables from other projects, list them here -->
 
* dpdk-16.11 release
 
* CSIT functional and performance tests available, with adequate coverage
 

Latest revision as of 14:12, 20 September 2016