Difference between revisions of "Projects/vpp/Release Plans/Release Plan 16.06"
From fd.io
m (→Release Milestones) |
m (→Expected Dependencies on Other Projects) |
||
| Line 48: | Line 48: | ||
| 16.06 artifacts available | | 16.06 artifacts available | ||
|} | |} | ||
| + | |||
| + | == Once we've pulled the 16.06 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 | ||
== Expected Dependencies on Other Projects == | == Expected Dependencies on Other Projects == | ||
| Line 53: | Line 63: | ||
<!-- If your project depends on other projects, and particularly specific deliverables from other projects, list them here --> | <!-- If your project depends on other projects, and particularly specific deliverables from other projects, list them here --> | ||
* dpdk-16.04 release | * dpdk-16.04 release | ||
| − | * CSIT functional and performance tests available, with adequate coverage | + | * CSIT functional and performance tests available, with adequate coverage |
== Compatibility with Previous Release == | == Compatibility with Previous Release == | ||
Revision as of 12:47, 16 May 2016
Contents
Introduction
Release Deliverables
| Name | Description |
|---|---|
| dpdk-16.04 | Support for the April 2016 dpdk release |
| IP-FIB-functional | glean adjacencies, indirect adjacencies, adjacency sharing, mitigate multi-thread barrier sync requirements |
| Packaging | acceptable for upstreaming to RH, Debian |
| Performance | characterize and document performance for this release |
Release Milestones
| Milestone | Date (UPDATED 4/12/2016) | Deliverables |
|---|---|---|
| F0 | 4/29/2016 | Only low-risk changes accepted on main branch. |
| RC0 | 5/16/2016 | Code complete, APIs frozen, 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. |
| RC1 | 5/31/2016 | Second artifacts posted. |
| Formal Release | 6/17/2016 | 16.06 artifacts available |
Once we've pulled the 16.06 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
Expected Dependencies on Other Projects
- dpdk-16.04 release
- CSIT functional and performance tests available, with adequate coverage
Compatibility with Previous Release
- N/A - first release.
