Difference between revisions of "Projects/vpp/Release Plans/Release Plan 21.10"
From fd.io
(→Release Milestones) |
(→Introduction) |
||
| Line 1: | Line 1: | ||
== Introduction == | == Introduction == | ||
| − | + | This page tracks release information for 21.10 | |
== Release Deliverables == | == Release Deliverables == | ||
Revision as of 12:22, 16 September 2021
Contents
Introduction
This page tracks release information for 21.10
Release Deliverables
See https://github.com/vpp-dev/vpp-release-notes for information.
Release Milestoneslink title
The milestones' start time will be at 12:00 UTC on the day of the milestone.
| Milestone | Date | Deliverables |
|---|---|---|
| RC1 | 2021-09-22 | 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 | 2021-10-13 (RC1+21) | Second artifacts posted. |
| Release gate | 2021-10-20 (RC2+7) | Deadline for patches destined for the release |
| Formal Release | 2021-10-27 (RC2+14) | 21.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 21.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, 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 externally found 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
