Release Schedule
================
-In an attempt to synchronize with other related open source projects
-(e.g., OPNFV and OpenStack), OpenDaylight releases twice per year on
-a 6 month cadence. These releases are scheduled for September 7th
-and March 7th. These release dates are also used as the beginning
-for the subsequent release.
+OpenDaylight releases twice per year. The six-month cadence is designed to
+synchronize OpenDaylight releases with OpenStack and OPNFV releases. Dates
+are adjusted to match current resources and requirements from the current
+OpenDaylight users. Dates are also adjusted when they conflict with holidays,
+overlap with other releases or are otherwise problematic.
+Dates are the release deadlines intended for managed projects.
+Self-managed projects that wants to integrate the distribution have one week
+to release once managed projects are ready.
+
+Each milestone is usually evaluated at a TSC meeting, which dictates deadlines.
+Nominal deadline is midnight UTC on the particular date. As an example, a date
+of 2022-10-06 means that all deliverables are due no later than
+2022-10-06T00:00:00Z. The corresponding TSC meeting happens either on
+9am or 10pm Pacific time. The slack time between the deadline and the actual call
+can be used for justified last-minute work if the need arises (though in general
+WE SHOULD NEVER need it). If such last-minute work results in a SimRel candidate
+build not being available, the reasons for that need to be discussed at,
+and documented as part of, the corresponding TSC meeting.
.. list-table::
- :widths: 20 20 20 40
+ :widths: 20 20 20 20 20 20 40
:header-rows: 1
:stub-columns: 1
- * - **Milestone**
- - **Time**
- - **Fluorine**
+ * - **Event**
+ - **2024.09 Scandium Dates**
+ - **2024.03 Calcium Dates**
+ - **2023.09 Potassium Dates**
+ - **Relative Dates**
+ - **Start-Relative Dates**
- **Description**
* - Release Start
+ - 2024-03-14
+ - 2023-09-14
+ - 2023-03-16
- Start Date
- - 2018-03-07
- - Declare Intention: Submit **Project_Plan** Jira item in TSC project
-
+ - Start Date +0
+ - Declare Intention: Submit **Project_Plan** Jira item in TSC project.
* - Initial Checkpoint
- - Start Date + 2 weeks
- - 2018-03-22
+ - 2024-03-28
+ - 2023-10-05
+ - 2023-03-30
+ - Start Date +2 weeks
+ - Start Date +2 weeks
- Initial Checkpoint. All Managed Projects must have completed
**Project_Plan** Jira items in TSC project.
-
* - Release Integrated Deadline
+ - 2024-04-16
+ - 2023-10-19
+ - 2023-04-20
- Initial Checkpoint + 2 weeks
- - 2018-04-07
- - Deadline for Release Integrated Projects (currently ODLPARENT and
- YANGTOOLS) to provide the desired version deliverables for downstream
- Snapshot Integrated Projects to consume.
-
+ - Start Date +4 weeks
+ - Deadline for Release Integrated Projects (currently, ODLPARENT,
+ YANGTOOLS, MDSAL, CONTROLLER and INFRAUTILS) to provide the desired
+ version deliverables for downstream Snapshot Integrated Projects to
+ consume.
* - Version Bump
+ - 2024-04-19
+ - 2023-10-20
+ - 2023-04-21
- Release Integrated Deadline + 1 day
- - 2018-04-08
+ - Start Date +4 weeks 1 day
- Prepare version bump patches and merge them in (RelEng team). Spend the
next 2 weeks to get green build for all MSI Projects and a healthy
distribution.
-
* - Version Bump Checkpoint
+ - 2024-04-25
+ - 2023-11-02
+ - 2023-04-27
- Release Integrated Deadline + 2 weeks
- - 2018-04-21
+ - Start Date +6 weeks
- Check status of MSI Projects to see if we have green builds and a
healthy distribution. Revert the MRI deliverables if deemed necessary.
-
* - CSIT Checkpoint
+ - 2024-05-09
+ - 2023-11-16
+ - 2023-05-11
- Version Bump Checkpoint + 2 weeks
- - 2018-05-07
+ - Start Date +8 weeks
- All Managed Release CSIT should be in good shape - get all MSI Projects'
CSIT results as they were before the version bump. This is the final
opportunity to revert the MRI deliverables if deemed necessary.
-
* - Middle Checkpoint
- - CSIT Checkpoint + 8 weeks
- - 2018-07-05
+ - 2024-07-04
+ - 2024-01-11
+ - 2023-07-06
+ - CSIT Checkpoint + 8 weeks (sometimes +2 weeks to avoid December holidays)
+ - Start Date +16 weeks (sometimes +2 weeks to avoid December holidays)
- Checkpoint for status of Managed Projects - especially Snapshot
Integrated Projects.
-
* - Code Freeze
+ - 2024-08-01
+ - 2024-02-08
+ - 2023-08-03
- Middle Checkpoint + 4 weeks
- - 2018-08-07
+ - Start Date +20 weeks
- Code freeze for all Managed Projects - cut and lock release branch. Only
- allow blocker bugfixes in release branch.
-
+ allow blocker bug fixes in release branch.
* - Final Checkpoint
- - TSC meeting 2 weeks after Code Freeze
- - 2018-08-23
+ - 2024-08-15
+ - 2024-02-22
+ - 2023-08-17
+ - Code Freeze + 2 weeks
+ - Start Date +22 weeks
- Final Checkpoint for all Managed Projects.
-
* - Formal Release
+ - 2024-09-19
+ - 2024-03-14
+ - 2023-09-21
- 6 months after Start Date
- - 2018-09-07
- - Formal release
-
+ - Start Date +6 months
+ - Formal Release for Managed Projects. Self-managed projects usually are released a week later.
* - Service Release 1
- - 1 month after Formal Release
- - 2018-10-07
+ - 2024-10-24
+ - 2024-04-25
+ - 2023-10-26
+ - 1.5 month after Formal Release
+ - Start Date +7.5 months
- Service Release 1 (SR1)
-
* - Service Release 2
- - 2 months after SR1
- - 2018-12-07
+ - 2025-01-23
+ - 2024-07-25
+ - 2024-01-25
+ - 3 months after SR1
+ - Start Date +10.5 months
- Service Release 2 (SR2)
-
* - Service Release 3
- - 2 months after SR2
- - 2019-02-07
+ - 2025-05-08
+ - 2024-10-24
+ - 2024-05-09
+ - 4 months after SR2
+ - Start Date +14 months
- Service Release 3 (SR3)
-
- * - Service Release 4
- - 3 months after SR3
- - 2019-05-07
- - Service Release 4 (SR4) - final service release
-
+ * - Service Release 4 (optional, based on documented need)
+ - N/A
+ - N/A
+ - N/A
+ - Not Applicable
+ - Not Applicable
+ - Service Release 4 (SR4) - Final Service Release
* - Release End of Life
- - 4 months after SR4
- - 2019-09-07
+ - 2025-09-18
+ - 2025-03-25
+ - 2024-09-19
+ - 4 months after SR3
+ - Start Date +18 months
- End of Life - coincides with the Formal Release of the current release+2
- versions and the start of the current release+3 versions
+ versions and the start of the current release+3 versions.
Code Review / docs.git / blobdiff