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

From fd.io
Jump to: navigation, search
(→‎Release Milestones)
(→‎Release Milestones)
Line 48: Line 48:
  
 
<span style="color:#ff0000; font-size:75%">''NOTE: Dates chosen based on:''</span>
 
<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%">''mid-month release''</span>
−
<span style="color:#ff0000; font-size:75%">''* milestone + days''</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>
+
* <span style="color:#ff0000; font-size:75%">''day after VPP community meeting, for discussion, go/no-go''</span>
  
 
== Once we've pulled the 16.09 release throttle ==
 
== Once we've pulled the 16.09 release throttle ==

Revision as of 11:59, 8 June 2016

Introduction

DRAFT ONLY

Release Deliverables

Name Description
dpdk-16.07 Support for the July 2016 dpdk release
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 8/3/2016 Only low-risk changes accepted on main branch.
RC1 (F0+14) 8/17/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 (RC1+14) 8/31/2016 Second artifacts posted.
Formal Release (RC2+14) 9/14/2016 16.09 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

JIRA

Kanban Board

Bugs to be fixed in 16.09

This list generated using JIRA search:vpp issues:bugs release:1609

NEED JIRA/CONFLUENCE IMPORT HERE

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.07 release
  • CSIT functional and performance tests available, with adequate coverage

Compatibility with Previous Release

  • TBD

Themes and Priorities

Other

Retrieved from "https://wiki.fd.io/index.php?title=Projects/vpp/Release_Plans/Release_Plan_16.09&oldid=1721"