Difference between revisions of "Projects/vpp/Release Plans/Release Plan 19.01"
From fd.io
m |
|||
| Line 22: | Line 22: | ||
== Release Milestones == | == Release Milestones == | ||
<!-- <span style="font-size:120%">The schedule below is FINAL as agreed on Aug 21st during VPP project meeting</span> --> | <!-- <span style="font-size:120%">The schedule below is FINAL as agreed on Aug 21st during VPP project meeting</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. --> | <!-- 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. --> | ||
Revision as of 22:15, 8 January 2019
Contents
Introduction
This page tracks release information for 19.01
Release Deliverables
| Name | Description | Status |
|---|---|---|
| Deprecate old stats | Deprecate the event based counter infrastructure. | Done |
| New API types | Add specific API types for IP addresses, MAC address, interface index etc. | Done |
| Python 3 support | Add Python 3 support in API compiler, Python API wrappers, Test framework, and Packaging | In progress |
| Graph Dispatcher tracing | Capture packet data and buffer metadata, output in pcap format | Done |
Release Milestones
As agreed during the Jan 8 VPP project meeting, the milestones' time will be at 18:00 UTC on the day of the milestone.
| Milestone | Date | Deliverables |
|---|---|---|
| F0 | 2019-01-09 | APIs frozen. Only low-risk changes accepted on main branch. |
| RC1 | 2019-01-16 (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-01-23 (RC1 + 7) | Second artifacts posted. |
| Formal Release | 2019-01-30 (RC2 + 7) | 19.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 19.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.
Features to be added in 19.01
NEED JIRA/CONFLUENCE IMPORT HERE
