View source for UDPI/20.01 Release Plan

== Introduction ==

This page tracks release information for 20.01

== Release Deliverables ==

{|class="wikitable"
! Name
! Description
! Status

|-
| rowspan="2" | Framework  || Enhance build system || In-progress
|-
| Add Test Framework || 

|-
| rowspan="1" | Flow Classification  || HW Flow Offload || In-progress 

|-
| rowspan="1" | Video  || Video Apps detection ||

|-
| rowspan="1" | VoIP  || VoIP Apps detection ||

|-
| rowspan="1" | Test  || VoIP Apps detection ||

|-
| rowspan="1" | DNS  || DNS implementation ||  

|}

== Release Milestones ==
<span style="font-size:120%">The schedule below is DRAFT </span>

<!-- As agreed during the Jan 8 VPP project meeting, -->
the milestones' time will be at <b>18:00 UTC</b> on the day of the milestone.

<!-- It is not uncommon for a project as part of its release process to have Milestones (M0, M1, M2, RC0, RC1) with corresponding events which occur at various milestones (API Freeze, Code Freeze, etc).  This is the place to list Milestones, their expected dates, and their expected events (whether process events, API Freeze, or noting a deliverable is coming in at a particular event. -->

{| class="wikitable"
! 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 
|}

<span style="color:#ff0000; font-size:75%">''NOTE: Dates chosen based on:''</span>
* <span style="color:#ff0000; font-size:75%">''end-month release''</span>
* <span style="color:#ff0000; font-size:75%">''milestone + days''</span>
* <span style="color:#ff0000; font-size:75%">''release date after VPP community meeting, for discussion, go/no-go''</span>

== 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.

<span style="color:#ff0000; font-size:100%"><div style="text-align:center">NEED JIRA/CONFLUENCE IMPORT HERE</div></span>

== Expected Dependencies on Other Projects ==