Difference between revisions of "Projects/vpp/Release Plans/Release Plan 24.10"
From fd.io
(Created page with "== Introduction == This page tracks release information for 24.10 == Release Deliverables == See https://github.com/vpp-dev/vpp-release-notes for information. == Release Mi...") |
|||
| Line 35: | Line 35: | ||
* <span style="color:#ff0000; font-size:75%">''release date after VPP community meeting, for discussion, go/no-go''</span> | * <span style="color:#ff0000; font-size:75%">''release date after VPP community meeting, for discussion, go/no-go''</span> | ||
| − | == Once we've pulled the 24. | + | == Once we've pulled the 24.10 release throttle == |
We need to be disciplined with respect to bugfix commits. Here are a few common-sense suggestions: | We need to be disciplined with respect to bugfix commits. Here are a few common-sense suggestions: | ||
Revision as of 13:59, 22 July 2024
Contents
Introduction
This page tracks release information for 24.10
Release Deliverables
See https://github.com/vpp-dev/vpp-release-notes for information.
Release Milestones
The schedule below is TENTATIVE.
The milestones' start time will be at 12:00 UTC on the day of the milestone.
| Milestone | Date | Deliverables |
|---|---|---|
| RC1 | 2024-09-25 | 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 | 2024-10-16 (RC1+21) | Second artifacts posted. |
| Formal Release | 2024-10-30 (RC2+14) | 24.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 24.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.
