Difference between revisions of "Projects/vpp/Release Plans/Release Plan 18.10"
From fd.io
| Line 15: | Line 15: | ||
== Release Milestones == | == Release Milestones == | ||
| − | <span style=" | + | <span style="font-size:120%">The schedule below is FINAL as agreed on Aug 21st during VPP project meeting</span> |
<!-- 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 15:33, 21 August 2018
Contents
Introduction
This page tracks release information for 18.10
Release Deliverables
| Name | Description | Status |
|---|---|---|
| INFRA | DPDK 18.08 integration |
Release Milestones
The schedule below is FINAL as agreed on Aug 21st during VPP project meeting
| Milestone | Date | Deliverables |
|---|---|---|
| F0 | 2018-10-03 | APIs frozen. Only low-risk changes accepted on main branch. |
| RC1 | 2018-10-10 (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 | 2018-10-17 (RC1 + 7) | Second artifacts posted. |
| Formal Release | 2018-10-24 (RC2 + 7) | 18.10 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 18.10 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.10
NEED JIRA/CONFLUENCE IMPORT HERE
