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

From fd.io
Jump to: navigation, search
(Release Deliverables)
(Release Deliverables)
Line 23: Line 23:
  
 
|-
 
|-
| rowspan="3" | Feature || Description || Done
+
| rowspan="4" | Host Stack || SVM fifo sizing (first cut implementation done) || In-progress
 
|-
 
|-
| Major refactor/cleanup of session layer. || Done
+
| Global output scheduler for session layer || In-progress
 
|-
 
|-
| Major refactor/cleanup of session layer. || Done
+
| TCP delivery rate estimator || In-progress
 +
|-
 +
| TCP ack/retransmission/syn generation improvements || In-progress
 
|-
 
|-
 
|}
 
|}

Revision as of 08:56, 3 July 2019

Introduction

This page tracks release information for 19.08

Release Deliverables

Name Description Status
Feature Description Done
Feature Description Done
Feature Description Done
Feature Description Done
Host Stack SVM fifo sizing (first cut implementation done) In-progress
Global output scheduler for session layer In-progress
TCP delivery rate estimator In-progress
TCP ack/retransmission/syn generation improvements In-progress

Release Milestones

The schedule below is DRAFT

the milestones' time will be at 18:00 UTC on the day of the milestone.


Milestone Date Deliverables
F0 2019-07-31 APIs frozen. Only low-risk changes accepted on main branch.
RC1 2019-08-07 (F0 + 7) 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 2019-08-14 (RC1 + 7) Second artifacts posted.
Formal Release 2019-08-21 (RC2 + 7) 19.08 release artifacts available

NOTE: Dates chosen based on:

  • end-month release
  • milestone + days
  • release date after VPP community meeting, for discussion, go/no-go

Once we've pulled the 19.08 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 for commits into the stable branch and master.
NEED JIRA/CONFLUENCE IMPORT HERE


Expected Dependencies on Other Projects