Difference between revisions of "Sweetcomb/20.01 Release Plan"
From fd.io
(Created page with "== Introduction == This page tracks release information for 19.08 == Release Deliverables == {|class="wikitable" ! Name ! Description ! Status |- | rowspan="1" | NAT || N...") |
(→Once we've pulled the 19.08 release throttle) |
||
Line 49: | Line 49: | ||
* <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 | + | == Once we've pulled the 20.01 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: | ||
Line 60: | Line 60: | ||
<span style="color:#ff0000; font-size:100%"><div style="text-align:center">NEED JIRA/CONFLUENCE IMPORT HERE</div></span> | <span style="color:#ff0000; font-size:100%"><div style="text-align:center">NEED JIRA/CONFLUENCE IMPORT HERE</div></span> | ||
− | |||
== Expected Dependencies on Other Projects == | == Expected Dependencies on Other Projects == |
Revision as of 07:19, 17 September 2019
Contents
[hide]Introduction
This page tracks release information for 19.08
Release Deliverables
Name | Description | Status |
---|---|---|
NAT | NAT YANG Model |
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 | 2020-01-07 | APIs frozen. Only low-risk changes accepted on main branch. |
RC1 | 2020-01-14 (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-01-21 (RC1 + 7) | Second artifacts posted. |
Formal Release | 2020-01-28 (RC2 + 7) | 20.01 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.01 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