|
|
| Line 1: |
Line 1: |
| − | | + | See [[Projects/vpp/Release_Plans/Release_Plan_18.01 | 18.01 Release Plan]]. |
| − | | + | |
| − | == Introduction ==
| + | |
| − | | + | |
| − | | + | |
| − | | + | |
| − | This page tracks release information for 18.02.
| + | |
| − | | + | |
| − | | + | |
| − | == Release Deliverables ==
| + | |
| − | | + | |
| − | {|class="wikitable"
| + | |
| − | ! Name
| + | |
| − | ! Description
| + | |
| − | |-
| + | |
| − | |Infra
| + | |
| − | |DPDK 17.11 integration
| + | |
| − | | + | |
| − | |-
| + | |
| − | |VNET
| + | |
| − | |TBD
| + | |
| − | | + | |
| − | |-
| + | |
| − | |SNAT / NAT
| + | |
| − | |TBD
| + | |
| − | | + | |
| − | |-
| + | |
| − | |API
| + | |
| − | |TBD
| + | |
| − |
| + | |
| − | |-
| + | |
| − | |Host stack
| + | |
| − | |VPP TCP stack - scale / congestion
| + | |
| − | | + | |
| − | VPP Comms Library (VLC)
| + | |
| − | | + | |
| − | |-
| + | |
| − | |ONE-LISP
| + | |
| − | |TBD
| + | |
| − | | + | |
| − | |-
| + | |
| − | |PPPoE
| + | |
| − | |TBD
| + | |
| − | | + | |
| − | |}
| + | |
| − | | + | |
| − | == Release Milestones ==
| + | |
| − | | + | |
| − | <!-- 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
| + | |
| − | | 2018-01-10
| + | |
| − | | APIs frozen. Only low-risk changes accepted on main branch. | + | |
| − | |-
| + | |
| − | | RC1
| + | |
| − | | 2018-01-24 (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-02-07 (RC1+14)
| + | |
| − | | Second artifacts posted.
| + | |
| − | |-
| + | |
| − | | Formal Release
| + | |
| − | | 2018-02-21 (RC2+14)
| + | |
| − | | 18.02 artifacts available
| + | |
| − | |}
| + | |
| − | | + | |
| − | <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%">''milestone + days''</span>
| + | |
| − | * <span style="color:#ff0000; font-size:75%">''day after VPP community meeting, for discussion, go/no-go''</span>
| + | |
| − | | + | |
| − | == Once we've pulled the 18.02 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
| + | |
| − | | + | |
| − | | + | |
| − | === Features to be added in 18.02 ===
| + | |
| − | | + | |
| − | | + | |
| − | <span style="color:#ff0000; font-size:100%"><div style="text-align:center">NEED JIRA/CONFLUENCE IMPORT HERE</div></span>
| + | |
| − | | + | |
| − | == Expected Dependencies on Other Projects ==
| + | |
