Difference between revisions of "Projects/vpp/Release Plans/Release Plan 22.02"

From fd.io
Jump to: navigation, search
(Created page with "== Introduction == This page tracks release information for 22.02 == Release Deliverables == See https://github.com/vpp-dev/vpp-release-notes for information. == Release M...")
 
(Release Milestones)
 
Line 9: Line 9:
 
== Release Milestones ==
 
== Release Milestones ==
 
<!-- <span style="font-size:120%">The schedule below is FINAL, agreed on during the VPP community meeting 13 Oct 2020.</span> -->
 
<!-- <span style="font-size:120%">The schedule below is FINAL, agreed on during the VPP community meeting 13 Oct 2020.</span> -->
 
+
<span style="font-size:120%">The schedule below is TENTATIVE, to be confirmed at the next VPP community meeting.</span>
  
 
The milestones' start time will be at <b>12:00 UTC</b> on the day of the milestone.
 
The milestones' start time will be at <b>12:00 UTC</b> on the day of the milestone.

Latest revision as of 11:43, 17 November 2021

Introduction

This page tracks release information for 22.02

Release Deliverables

See https://github.com/vpp-dev/vpp-release-notes for information.


Release Milestones

The schedule below is TENTATIVE, to be confirmed at the next VPP community meeting.

The milestones' start time will be at 12:00 UTC on the day of the milestone.

Milestone Date Deliverables
RC1 2021-01-19 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 2022-02-09 (RC1+21) Second artifacts posted.
Release gate 2022-02-16 (RC2+7) Deadline for patches destined for the release
Formal Release 2022-02-23 (RC2+14) 22.02 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 22.02 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

Expected Dependencies on Other Projects