Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 113 Next »

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."

Latest Open edX Release

The latest supported release line is Hawthorn, based on code from 2018-07-03.

All Open edX Releases

Note that the latest release (Hawthorn) 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.

Release NameRelease DateGit Tag
Hawthorn: based on code from 2018-07-03.
Hawthorn.22018-09-26open-release/hawthorn.2
Hawthorn.12018-08-07open-release/hawthorn.1Devstack is now based on Docker

Ginkgo (unsupported): based on code from 2017-07-06. Latest changes are on open-release/ginkgo.master




Vagrant Box Files



Releases before Hawthorn had Vagrant box files.
Hawthorn and beyond do not.
Not every release needed 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.

GInkgo.22017-12-18open-release/ginkgo.2
  • devstack: box name: ginkgo-devstack-2017-07-14 *
    sha1: a7e3fce6d0155cde28e9f3253103f3f66ba3ea54

  • fullstack: box name: ginkgo-fullstack-2017-12-14
    sha1: c05fcd63df5fae452f0c8cb84720317449215472

Ginkgo.1

2017-08-14

open-release/ginkgo.1

  • devstack: box name: ginkgo-devstack-2017-07-14
    sha1: a7e3fce6d0155cde28e9f3253103f3f66ba3ea54

  • fullstack: box name: ginkgo-fullstack-2017-08-14
    sha1: 990d5fdb5bbc7683c158dd99d5732064932c9cdd

Ficus (unsupported): based on code from 2017-01-10. Latest changes are on open-release/ficus.master

Ficus.4

2017-08-10

open-release/ficus.4

  • devstack: box name: ficus-devstack-2017-02-07 *
    sha1: a7fb2200ccdb9f847bee7acd97f5e4e1434776b3

  • fullstack: box name: ficus-fullstack-2017-08-10
    sha1: c9f59b27b39339d12fcf008f7c5721c2970a57bd 

Ficus.3

2017-04-21

open-release/ficus.3

  • devstack: box name: ficus-devstack-2017-02-07 *
    sha1: a7fb2200ccdb9f847bee7acd97f5e4e1434776b3

  • fullstack: box name: ficus-fullstack-2017-04-20
    sha1: 64eb0a247d99454bccf0eed7ec49b076cbb9cd69 

Ficus.2

2017-03-29

open-release/ficus.2

  • devstack: box name: ficus-devstack-2017-02-07 *
    sha1: a7fb2200ccdb9f847bee7acd97f5e4e1434776b3

  • fullstack: box name: ficus-fullstack-2017-03-28
    sha1: fc6aa0d3b686c83e38e8c7fa1b1f172fcf7f71c1 

Ficus.1

2017-02-23

open-release/ficus.1

  • devstack: box name: ficus-devstack-2017-02-07
    sha1: a7fb2200ccdb9f847bee7acd97f5e4e1434776b3

  • fullstack: box name: ficus-fullstack-2017-02-15
    sha1: cd6310ffc1e6b374d2c3d59aab5191500f9d5d6f 
Eucalyptus (unsupported): based on code from 2016-07-13. Latest changes on open-release/eucalyptus.master
Eucalyptus.32017-01-10

open-release/eucalyptus.3

  • devstack: box name: eucalyptus-devstack-2016-09-01 *
    sha1: a26c8fdbb431279863654161d0145732ee36ed66 
  • fullstack: box name: eucalyptus-fullstack-2017-01-10
    sha1: 64fd2a6efd656a7170127cccdf4458699ea04978 
Eucalyptus.22016-09-02

open-release/eucalyptus.2

  • devstack: box name: eucalyptus-devstack-2016-09-01
  • fullstack: box name: eucalyptus-fullstack-2016-09-01

Eucalyptus.1

2016-08-26

open-release/eucalyptus.1

  • devstack: box name: eucalyptus-devstack-2016-08-19
  • fullstack: box name: eucalyptus-fullstack-2016-08-25

Dogwood (unsupported): based on code from 2015-12-15. Latest changes on named-release/dogwood.rc

Dogwood.32016-04-25

named-release/dogwood.3

  • devstack: box name: dogwood-devstack-2016-03-09 *
  • fullstack: box name: dogwood-fullstack-rc2 *
Dogwood.22016-04-14

named-release/dogwood.2

  • devstack: box name: dogwood-devstack-2016-03-09 *
  • fullstack: box name: dogwood-fullstack-rc2 *
Dogwood.12016-03-09

named-release/dogwood.1

  • devstack: box name: dogwood-devstack-2016-03-09
  • fullstack: box name: dogwood-fullstack-rc2 *

Dogwood

2016-02-11

named-release/dogwood

Cypress (unsupported): based on code from 2015-07-07. Latest changes on named-release/cypress.rc

Cypress

2015-08-13named-release/cypress
Birch (unsupported): based on code from 2015-01-29. Latest changes on named-release/birch.rc

Birch.2

2015-08-05named-release/birch.2
Birch.12015-07-27named-release/birch.1
Birch2015-02-24named-release/birch
Aspen (unsupported): based on code from 2014-09-05.
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 on 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.

Feedback

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!


  • No labels