Difference between revisions of "Sweetcomb/20.01 Release Plan"

From fd.io
Jump to: navigation, search
(Release Deliverables)
(Release Deliverables)
 
(4 intermediate revisions by the same user not shown)
Line 11: Line 11:
  
 
|-
 
|-
| rowspan="1" | NAT  || NAT YANG Model ||  
+
| rowspan="2" | Restconf  || Restconf implementation || In-progress
 +
|-
 +
| Migrate into Netopeer2 Project || In-progress
 +
 
 +
|-
 +
| rowspan="1" | NAT  || NAT YANG Model || In-progress
  
 
|-
 
|-

Latest revision as of 07:29, 17 September 2019

Introduction

This page tracks release information for 20.01

Release Deliverables

Name Description Status
Restconf Restconf implementation In-progress
Migrate into Netopeer2 Project In-progress
NAT NAT YANG Model In-progress
FIB FIB YANG Model

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 2020-01-07 APIs frozen. Only low-risk changes accepted on main branch.
RC1 2020-01-14 (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 2020-01-21 (RC1 + 7) Second artifacts posted.
Formal Release 2020-01-28 (RC2 + 7) 20.01 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 20.01 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