Difference between revisions of "Honeycomb/Release Plans/Release Plan 16.09"
From fd.io
(→Release Deliverables) |
(→Release Milestones) |
||
Line 53: | Line 53: | ||
{| class="wikitable" | {| class="wikitable" | ||
! Milestone | ! Milestone | ||
− | ! Date (UPDATED | + | ! Date (UPDATED 5/19/2016) |
! Deliverables | ! Deliverables | ||
|- | |- |
Revision as of 09:01, 19 May 2016
Contents
Introduction
16.06 Release of Honeycomb is it's first official release. Relying on VPP's 16.06 release. Included in this release is the migration of vbd application into ODL's dedicated project. Code freeze milestone for vbd in ODL is 7/21/2016.
Release Deliverables
Release Milestones
Milestone | Date (UPDATED 5/19/2016) | Deliverables |
---|---|---|
F0 | 6/20/2016 | Only low-risk changes accepted on main branch. |
RC1 | 7/4/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. VBD in opendaylight published, using RC1 version of Honeycomb's artifacts. |
RC2 | 7/18/2016 | Second artifacts posted. |
Formal Release | 7/29/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
- ODL Beryllium-SR2 release
- VPP 16.06 release
- CSIT functional and performance tests available, with adequate coverage
Compatibility with Previous Release
- N/A - first release.