...
Release Name | Release Date | Git Tag | Vagrant Box Torrents |
---|---|---|---|
Eucalyptus.1rc21prerelease | 2016-08-1926 | open-release/eucalyptus.1rc21 |
|
Dogwood.3 | 2016-04-25 | named-release/dogwood.3 | NOTE: same as the dogwood.2 boxes |
Dogwood.2 | 2016-04-14 | named-release/dogwood.2 | NOTE: same as the dogwood.1 boxes |
Dogwood.1 | 2016-03-09 | named-release/dogwood.1 | NOTE: fullstack is the same as Dogwood, only devstack has changed. |
Dogwood | 2016-02-11 | named-release/dogwood | |
Cypress | 2015-08-13 | named-release/cypress | |
Birch.2 | 2015-08-05 | named-release/birch.2 | |
Birch.1 (unsupported) | 2015-07-27 | named-release/birch.1 | |
Birch (unsupported) | 2015-02-24 | named-release/birch | |
Aspen (unsupported) | 2014-10-28 | named-release/aspen |
Note that "release candidates" are not final yet, which is why they do not have a release date in this table. We encourage the Open edX community to test release candidates for several days and report any issues, so that they can be fixed before the new release is declared. In git, release candidates are branches, while releases are tags.
Eucalyptus Release (In Prerelease)
...
open-release/eucalyptus/1rc1
...
Installing an Open edX Release
The Open edX docs include Dogwood install instructions, and details of how to upgrade from Cypress to Dogwood.
Security Updates
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 security@edx.org. Please do not post the vulnerability to the public mailing lists.
...