Open edX Release Schedule
- Ned Batchelder (Deactivated)
- Jorge Londoño
- Matjaz Gregoric
Recent Schedule
Older release dates are archived in the official docs.
| Olive | Palm | 🍐 Quince | Redwood | 🌿 Sumac | 🌳 Teak | 🌿 Ulmo | 🌳🏵️ Verawood |
|---|---|---|---|---|---|---|---|---|
Thu 2022-10-10 | olive.master |
|
|
|
|
|
|
|
Mon 2022-12-12 | olive.1 |
|
|
|
|
|
|
|
Thu 2023-02-09 | olive.2 |
|
|
|
|
|
|
|
Mon 2023-04-11 | olive.3 | palm.master |
|
|
|
|
|
|
Mon 2023-06-14 | olive EOL | palm.1 |
|
|
|
|
|
|
Wed 2023-08-09 |
| palm.2 |
|
|
|
|
|
|
Tue 2023-10-10 |
|
| quince.master |
|
|
|
|
|
Fri 2023-10-13 |
| palm.3 |
|
|
|
|
|
|
Thu 2023-11-16 |
| palm.4 |
|
|
|
|
|
|
Mon 2023-12-11 |
| palm EOL | quince.1 |
|
|
|
|
|
Fri 2024-02-09 |
|
| quince.2 |
|
|
|
|
|
Tue 2024-04-09 |
|
| quince.3 |
|
|
|
|
|
Thu 2024-05-09 |
|
|
| redwood.master |
|
|
|
|
Wed 2024-06-19 |
|
| quince EOL | redwood.1 |
|
|
|
|
Fri 2024-08-09 |
|
|
| redwood.2 |
|
|
|
|
Wed 2024-10-23 |
|
|
| redwood.3 |
|
|
|
|
Thu 2024-10-24 |
|
|
|
| sumac.master |
|
|
|
~ 2024-12-16 |
|
|
| redwood EOL | sumac.1 |
|
|
|
~ 2025-02-12 |
|
|
|
| sumac.2 |
|
|
|
~ 2025-04-09 |
|
|
|
| sumac.3 | teak.master |
|
|
~ 2025-06-09 |
|
|
|
| sumac EOL | teak.1 |
|
|
~ 2025-08-09 |
|
|
|
|
| teak.2 |
|
|
~ 2025-10-09 |
|
|
|
|
| teak.3 | <ulmo.master> |
|
~ 2025-12-09 |
|
|
|
|
| teak EOL | <ulmo.1> |
|
~ 2026-02-09 |
|
|
|
|
|
| <ulmo.1> |
|
~ 2026-04-09 |
|
|
|
|
|
| <ulmo.1> |
|
The Schedule, Explained
Named versions of Open edX are released on a six-month schedule. Versions are named alphabetically after trees. In these docs we like to use Yucca and Zebrawood as hypothetical examples.
On April 9th and October 9th, each two months before a named release, we cut branches for the new named version and begin testing it. In other words, we freeze of a copy of the latest version of Open edX so that we can focus on stabilizing and documenting it.
On June 9th and December 9th, we announce the release of the new named version. When we are being specific, we append “.1” to the tree name, for example Zebrawood.1. At this point, we announce that the previous named version is no longer supported . For example, if we just released Zebrawood.1, then Yucca.* would no longer be supported.
On August 9th and February 9th, we do a point release of the most recent named version. The point release will be similar to the named version that came before it, but will include bug fixes and other minor improvements. We indicate it by appending “.2” to the tree name, for example, Zebrawood.2.
On October 9th and April 9th, we do another point release of the most recent named version. We indicate this one by appending “.3” to the tree name, for example, Zebrawood.3. At this point, we also cut branches for the next named version, thus restarting the cycle
If the 9th is a Friday, weekend, or holiday, then the release generally happens the following business day.
Example Timeline
Apr 9: Xylowood.3 is released and Yucca.master is cut.
Jun 9: Yucca.1 is released and Xylowood.* goes out of support.
Aug 9: Yucca.2 is released.
Oct 9: Yucca.3 is released and Zebrawood.master is cut.
Dec 9: Zebrawood.1 is released and Yucca.* goes out of support.
Feb 9: Zebrawood.2 is released.
…and so on