The Open edX community can share knowledge and improvements more easily when most people use the same stable, consistent version of the Open edX codebase. To that end, edX is creating a series of Open edX releases, which are distinct from the daily deployments to edx.org and have a longer release cycle (on the order of several months between each release). These releases will be tested both by edX and by the Open edX community, and with each subsequent release we will include instructions for how to upgrade from the previous Open edX release.
Open edX releases are also sometimes called "named releases."
Current Open edX Releases
Note that the latest release (Ficus) is the only supported release. We currently do not have the ability to support more than one release at a time.
For documentation on the latest release, please visit http://edx.readthedocs.org/projects/open-edx-release-notes/en/latest/
Every release line (Dogwood, Eucalyptus, etc) has a branch that accumulates changes destined for that release. When it is time to make a new release in the line, we tag that branch. When a release line is no longer supported, we might still add important fixes to the branch, but not make a new tagged release. At that point, someone installing that line will want to install from the branch, not the tags.
Not every release needs new box files. Box files the same as the previous release are marked with an asterisk *. Hashes are SHA1 hashes of the box file, not git commit hashes.
|Release Name||Release Date||Git Tag||Vagrant Box Files|
Ficus: based on code from 2017-01-10.
|Eucalyptus: based on code from 2016-07-13. Latest changes on open-release/eucalyptus.master|
Dogwood (unsupported): based on code from 2015-12-15. Latest changes on named-release/dogwood.rc
|Cypress (unsupported): based on code from 2015-07-07. Latest changes on named-release/cypress.rc|
|Birch (unsupported): based on code from 2015-01-29. Latest changes on named-release/birch.rc|
|Aspen (unsupported): based on code from 2014-09-05.|
Upcoming releases have wiki pages for engineers to collect information that will be needed for their release on the Open edX Release Planning page.
If security vulnerabilities or other serious problems (such as data loss) are discovered in the most recent Open edX release, edX will release a new version of that release that includes the fix. We will not make patches of any releases before the most recent one. We are still working on the details of how often to update Open edX releases. We will publicly announce the security issue, and encourage the Open edX community to update their installations to close the vulnerability. If you have found a security vulnerability in the Open edX codebase, please report it by sending an email to firstname.lastname@example.org. Please do not post the vulnerability to the public mailing lists.
If you find a problem in the release candidate, please report them on the mailing list (
openedx-ops for operations problem,
edx-code for other problems), or even better, create issues in JIRA. We are very interested to hear from the community about what you value about Open edX releases. Please let us know what you would like to see in future releases. Discussion on the mailing list is always welcome, of course!