Difference between revisions of "Projects/vpp/Release Plans/Release Plan 18.10"
From fd.io
| Line 33: | Line 33: | ||
|- | |- | ||
| RC2 | | RC2 | ||
| − | | 2018-10- | + | | 2018-10-17 (RC1 + 7) |
| Second artifacts posted. | | Second artifacts posted. | ||
|- | |- | ||
| Formal Release | | Formal Release | ||
| − | | 2018-10- | + | | 2018-10-24 (RC2 + 7) |
| 18.10 release artifacts available | | 18.10 release artifacts available | ||
|} | |} | ||
Revision as of 15:31, 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 still a DRAFT; to be agreed upon by the community at VPP meeting on Aug 21st
| 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
