Difference between revisions of "Projects/vpp/Release Plans/Release Plan 19.08"
From fd.io
(Created page with "== Introduction == This page tracks release information for 19.04 == Release Deliverables == {|class="wikitable" ! Name ! Description ! Status |- | rowspan="1" | Feature...") |
(→Introduction) |
||
| Line 1: | Line 1: | ||
== Introduction == | == Introduction == | ||
| − | This page tracks release information for 19. | + | This page tracks release information for 19.08 |
== Release Deliverables == | == Release Deliverables == | ||
Revision as of 10:42, 28 May 2019
Contents
Introduction
This page tracks release information for 19.08
Release Deliverables
| Name | Description | Status |
|---|---|---|
| Feature | Description | Done |
| Feature | Description | Done |
| Feature | Description | Done |
| Feature | Description | Done |
Release Milestones
The schedule below is DRAFT
the milestones' time will be at 18:00 UTC on the day of the milestone.
| Milestone | Date | Deliverables |
|---|---|---|
| F0 | 2019-07-31 | APIs frozen. Only low-risk changes accepted on main branch. |
| RC1 | 2019-08-07 (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-08-14 (RC1 + 7) | Second artifacts posted. |
| Formal Release | 2019-08-21 (RC2 + 7) | 19.08 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.08 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.
NEED JIRA/CONFLUENCE IMPORT HERE
