5 OpenDaylight releases twice per year. The six-month cadence is designed to
6 synchronize OpenDaylight releases with OpenStack and OPNFV releases. Dates
7 are adjusted to match current resources and requirements from the current
8 OpenDaylight users. Dates are also adjusted when they conflict with holidays,
9 overlap with other releases or are otherwise problematic.
10 Dates are the release deadlines intended for managed projects.
11 Self-managed projects that wants to integrate the distribution have one week
12 to release once managed projects are ready.
14 Each milestone is usually evaluated at a TSC meeting, which dictates deadlines.
15 Nominal deadline is midnight UTC on the particular date. As an example, a date
16 of 2022-10-06 means that all deliverables are due no later than
17 2022-10-06T00:00:00Z. The corresponding TSC meeting happens either on
18 9am or 10pm Pacific time. The slack time between the deadline and the actual call
19 can be used for justified last-minute work if the need arises (though in general
20 WE SHOULD NEVER need it). If such last-minute work results in a SimRel candidate
21 build not being available, the reasons for that need to be discussed at,
22 and documented as part of, the corresponding TSC meeting.
25 :widths: 20 20 20 20 20 20 40
30 - **2024.03 Argon Dates**
31 - **2024.03 Calcium Dates**
32 - **2023.09 Potassium Dates**
34 - **Start-Relative Dates**
43 - Declare Intention: Submit **Project_Plan** Jira item in TSC project.
44 * - Initial Checkpoint
50 - Initial Checkpoint. All Managed Projects must have completed
51 **Project_Plan** Jira items in TSC project.
52 * - Release Integrated Deadline
56 - Initial Checkpoint + 2 weeks
58 - Deadline for Release Integrated Projects (currently, ODLPARENT,
59 YANGTOOLS, MDSAL, CONTROLLER and INFRAUTILS) to provide the desired
60 version deliverables for downstream Snapshot Integrated Projects to
66 - Release Integrated Deadline + 1 day
67 - Start Date +4 weeks 1 day
68 - Prepare version bump patches and merge them in (RelEng team). Spend the
69 next 2 weeks to get green build for all MSI Projects and a healthy
71 * - Version Bump Checkpoint
75 - Release Integrated Deadline + 2 weeks
77 - Check status of MSI Projects to see if we have green builds and a
78 healthy distribution. Revert the MRI deliverables if deemed necessary.
83 - Version Bump Checkpoint + 2 weeks
85 - All Managed Release CSIT should be in good shape - get all MSI Projects'
86 CSIT results as they were before the version bump. This is the final
87 opportunity to revert the MRI deliverables if deemed necessary.
92 - CSIT Checkpoint + 8 weeks (sometimes +2 weeks to avoid December holidays)
93 - Start Date +16 weeks (sometimes +2 weeks to avoid December holidays)
94 - Checkpoint for status of Managed Projects - especially Snapshot
100 - Middle Checkpoint + 4 weeks
101 - Start Date +20 weeks
102 - Code freeze for all Managed Projects - cut and lock release branch. Only
103 allow blocker bug fixes in release branch.
108 - Code Freeze + 2 weeks
109 - Start Date +22 weeks
110 - Final Checkpoint for all Managed Projects.
115 - 6 months after Start Date
116 - Start Date +6 months
117 - Formal Release for Managed Projects. Self-managed projects usually are released a week later.
118 * - Service Release 1
122 - 1.5 month after Formal Release
123 - Start Date +7.5 months
124 - Service Release 1 (SR1)
125 * - Service Release 2
130 - Start Date +10.5 months
131 - Service Release 2 (SR2)
132 * - Service Release 3
137 - Start Date +14 months
138 - Service Release 3 (SR3)
139 * - Service Release 4 (optional, based on documented need)
145 - Service Release 4 (SR4) - Final Service Release
146 * - Release End of Life
151 - Start Date +18 months
152 - End of Life - coincides with the Formal Release of the current release+2
153 versions and the start of the current release+3 versions.