While OpenDaylight has always targeted two releases per year, in practice our release process for the first six releases (through Carbon) has, in practice, released approximately every 8 months. This has meant we don’t quite release twice a year (Lithium was our only release in 2015) and we struggle to coordinate releases with other projects that release at regular times each year, e.g., OpenStack and OPNFV.
To try to fix this, we are having a short Nitrogen release and then moving to a date-based, six-month release calendar releasing at the same time each year.
| milestone | offset 0 | offset 1 | offset 2 | description |
|---|---|---|---|---|
| M0/M1 | 6/7/2017 | 6/14/2017 | 6/21/2017 | Draft Release Plan |
| M2/M3/M4 | 6/28/2017 | 7/7/2017 | 7/14/2017 | Final Release Plan, Functionality Freeze, API Freeze |
| M5 | 7/28/2017 | 8/7/2017 | 8/14/2017 | Code Freeze |
| RC0 | 8/14/2017 | |||
| RC1 | 8/14/2017 | |||
| RC2 | 8/14/2017 | |||
| RC3 | 8/14/2017 | |||
| Release | 9/7/2017 | |||
| SR1 | 10/7/2017 | |||
| SR2 | 12/7/2017 | |||
| SR3 | 2/7/2018 | |||
| SR4 | 3/21–5/7 |
Note
Dates are calendar based on the 7th, 14th, 21st, and 28th of each month instead of being on a particular day of the week. The intent is that projects will figure out how to meet the deadline in the way that best works for them even if that means getting work done ahead of time to avoid holidays, weekends, vacation or travel.
Starting with Oxygen, our odd-numbered element releases will look like this:
| milestone | off0 | off1 | off2 | Description |
|---|---|---|---|---|
| M0 | 9/7 | Draft Release Plan | ||
| M1 | 10/7 | 10/14 | 10/21 | Final Release Plan, Project Setup |
| M2 | 11/7 | 11/14 | 11/21 | Functionality Freeze |
| M3 | 12/7 | 12/14 | 12/21 | API Freeze |
| M4 | 1/7 | 1/14 | 1/21 | Code Freeze (note M3-M4 will likely be short since it includes 12/25-1/1) |
| RCs | 1/21-3/7 | (continuous build) | ||
| release | 3/7 | |||
| SR1 | 4/7 | |||
| SR2 | 6/7 | |||
| SR3 | 8/7 | |||
| SR4 | 9/21-11/7 |
Starting with Fluorine, our even-numbered element releases will look like this:
| milestone | off0 | off1 | off2 | Description |
|---|---|---|---|---|
| M0 | 3/7 | Draft Release Plan | ||
| M1 | 4/7 | 4/14 | 4/21 | Final Release Plan, Project Setup |
| M2 | 5/7 | 5/14 | 5/21 | Functionality Freeze |
| M3 | 6/7 | 6/14 | 6/21 | API Freeze |
| M4 | 7/7 | 7/14 | 7/21 | Code Freeze |
| RCs | 7/21-9/7 | (continuous build) | ||
| release | 9/7 | |||
| SR1 | 10/7 | |||
| SR2 | 12/7 | |||
| SR3 | 2/7 | |||
| SR4 | 3/21-5/7 |
