Difference between revisions of "Projects/vpp/Release Plans/Release Plan 20.09"
From fd.io
(Created page with "== Introduction == This page tracks release information for 20.09 == Release Deliverables == <!-- {|class="wikitable" ! Name ! Description ! Status |- | rowspan="1" | f...") |
(→Release Milestones) |
||
| Line 50: | Line 50: | ||
| Second artifacts posted. | | Second artifacts posted. | ||
|- | |- | ||
| − | | | + | | Cooldown and external tests |
| 2020-09-16 (RC2+7) | | 2020-09-16 (RC2+7) | ||
| Deadline for patches destined for the release | | Deadline for patches destined for the release | ||
Revision as of 12:08, 3 June 2020
Contents
Introduction
This page tracks release information for 20.09
Release Deliverables
Release Milestones
the milestones' time will be at 18:00 UTC on the day of the milestone.
| Milestone | Date | Deliverables |
|---|---|---|
| F0 | 2020-09-02 | APIs frozen. Only low-risk changes accepted on main branch. |
| RC1 | 2020-09-09 (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 | 2020-09-16 (RC1+7) | Second artifacts posted. |
| Cooldown and external tests | 2020-09-16 (RC2+7) | Deadline for patches destined for the release |
| Formal Release | 2020-09-30 (RC2+14) | 20.09 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 20.09 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, and 19.08 LTS, and the master branch
- Commit first to the master branch, then "git cherry-pick" into release throttle
- 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
