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

From fd.io
Jump to: navigation, search
m (Expected Dependencies on Other Projects)
m (Release Milestones)
 
Line 36: Line 36:
 
| Only low-risk changes accepted on main branch.   
 
| Only low-risk changes accepted on main branch.   
 
|-
 
|-
| RC0
+
| RC1
 
| 5/16/2016
 
| 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.  
 
| 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
+
| RC2
 
| 5/31/2016
 
| 5/31/2016
 
| Second artifacts posted.  
 
| Second artifacts posted.  

Latest revision as of 15:39, 17 May 2016

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.
RC1 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.
RC2 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.

Themes and Priorities

Other