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

From fd.io
Jump to: navigation, search
(→‎Release Deliverables)
m (→‎Release Deliverables)
Line 20: Line 20:
 
|-
 
|-
 
| rowspan="1" | API || "Show Run" stats api refactoring (VPP-55) || Backlog
 
| rowspan="1" | API || "Show Run" stats api refactoring (VPP-55) || Backlog
 +
|-
 +
                    || Unicast and Broadcast stats || In Progress
  
 
|-
 
|-

Revision as of 08:08, 20 February 2018

Introduction

This page tracks release information for 18.04.

Release Deliverables

Name Description Status
INFRA DPDK 18.02 integration In Progress
VNET SCTP In Progress
ERSPAN Done
API "Show Run" stats api refactoring (VPP-55) Backlog
Unicast and Broadcast stats In Progress
HOSTSTACK Secure attach / segment mgmt In Progress
VCL Envoy Integration In Progress
VCL Logging / tracing refactoring In Progress
VCL CI test integration In Progress
BITBUCKET Boiling the Ocean Deferred to 18.07

Release Milestones

Milestone Date Deliverables
F0 2018-03-21 APIs frozen. Only low-risk changes accepted on main branch.
RC1 2018-04-04 (F0+14) 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 2018-04-11 (RC1+7) Second artifacts posted.
Formal Release 2018-04-25 (RC2+14) 18.04 release 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 18.04 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.


Features to be added in 18.04

NEED JIRA/CONFLUENCE IMPORT HERE

Expected Dependencies on Other Projects

Retrieved from "https://wiki.fd.io/index.php?title=Projects/vpp/Release_Plans/Release_Plan_18.04&oldid=6964"