Difference between revisions of "Projects/vpp/Release Plans/Release Plan 16.12"
From fd.io
Line 47: | Line 47: | ||
|- | |- | ||
| F0 | | F0 | ||
− | | | + | | 2016-12-07 |
| APIs frozen. Only low-risk changes accepted on main branch. | | APIs frozen. Only low-risk changes accepted on main branch. | ||
|- | |- | ||
| RC1 | | RC1 | ||
− | | (F0+14) | + | | 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. | | 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 | | RC2 | ||
− | | (RC1+14) | + | | 2017-01-04 (RC1+14) |
| Second artifacts posted. | | Second artifacts posted. | ||
|- | |- | ||
| Formal Release | | Formal Release | ||
− | | (RC2+14) | + | | 2017-01-18 (RC2+14) |
| 17.01 artifacts available | | 17.01 artifacts available | ||
|} | |} |
Revision as of 14:09, 20 September 2016
Contents
Introduction
Release Deliverables
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
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 |
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 16.09 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 16.09
This list generated using JIRA search:vpp issues:features/tasks release:1609
NEED JIRA/CONFLUENCE IMPORT HERE
Expected Dependencies on Other Projects
- dpdk-16.11 release
- CSIT functional and performance tests available, with adequate coverage