...
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 *.
| Release Name | Release Date | Git Tag | Vagrant Box Files | |
|---|---|---|---|---|
Ficus | ||||
Ficus.1 | 2017-02-23 | open-release/ficus.1 | ||
Eucalyptus: latest changes are on the open-release/eucalyptus.master branch | ||||
| Eucalyptus.3 | 2017-01-10 | open-release/eucalyptus.3 | ||
| Eucalyptus.2 | 2016-09-02 | open-release/eucalyptus.2 | ||
Eucalyptus.1 | 2016-08-26 | open-release/eucalyptus.1 | ||
Dogwood (unsupported): latest changes are on the | ||||
| Dogwood.3 | 2016-04-25 | named-release/dogwood.3 | ||
| Dogwood.2 boxes | Dogwood.2 | 2016-04-14 | named-release/dogwood.2 | |
| Dogwood.1 | 2016-03-09 | named-release/dogwood.1 | ||
Dogwood fullstack box fileDogwood | 2016-02-11 | named-release/dogwood | ||
| Cypress (unsupported) | ||||
Cypress | 2015-08-13 | named-release/cypress | ||
| Birch (unsupported) | ||||
Birch.2 | 2015-08-05 | named-release/birch.2 | ||
| Birch.1 | 2015-07-27 | named-release/birch.1 | ||
| Birch | 2015-02-24 | named-release/birch | ||
| Aspen (unsupported) | ||||
| Aspen | 2014-10-28 | named-release/aspen | ||
...
Future Releases
Upcoming releases have wiki pages for engineers to collect information that will be needed for their release : Ginkgo, Hawthornon the Open edX Release Planning page.
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.
...