The latest Open edX® release is Verawood (June 2026), preceded by Ulmo (December 2025). Open edX® follows a biannual release cycle with updates every June and December.
Verawood is the latest stable Open edX® release and the recommended version for new deployments.
Verawood focuses on platform maturity and operational stability. It strengthens production reliability while improving upgrade consistency and cloud-native deployment alignment.
🔎 In short: Verawood enhances scalability, reliability, and long-term maintainability.
Ulmo improved architectural consistency and simplified upgrade paths for institutions transitioning from older releases.
🔎 In short: Ulmo stabilized the modernization phase and enabled smoother future upgrades.
Ulmo consolidated earlier modernization efforts and prepared the platform for Verawood.
Teak helped consolidate modernization efforts introduced in earlier releases.
Ulmo consolidated earlier modernization efforts and prepared the platform for Verawood.
Teak helped consolidate modernization efforts introduced in earlier releases.
Redwood reinforced frontend modernization efforts and introduced system performance optimizations across LMS and Studio.
Redwood marked a significant step toward cloud-native readiness.
Quince focused on backend consolidation and long-term maintainability improvements.
Quince helped prepare the ecosystem for smoother migrations toward newer releases.
| Release | Year | Strategic Contribution |
|---|---|---|
| Nutmeg | 2021 | Performance optimization |
| Maple | 2021 | Frontend modernization groundwork |
| Lilac | 2021 | Pre-MFE stabilization phase |
| Koa | 2020 | Modernization groundwork |
| Juniper | 2020 | Backend performance improvements |
| Ironwood | 2019 | Security and stability focus |
| Hawthorn | 2018 | Enterprise enhancements |
| Ginkgo | 2017 | Usability improvements |
| Ficus | 2017 | Infrastructure improvements |
| Eucalyptus | 2016 | Early scalable LMS consolidation |
The latest Open edX® release is Verawood (June 2026). It is the recommended version for new deployments and production environments.
Open edX® publishes two named releases per year, typically in June and December.
Not necessarily every release, but organizations should upgrade at least once per year to avoid technical debt and security risks.
Running outdated versions can lead to security vulnerabilities, plugin incompatibility, performance degradation, and more complex future upgrades.
Older releases eventually become unsupported by the community. Staying within one release of the current stable version is considered best practice.
