Open edX Named Release Branches and Tags#

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, the Build-Test-Release working group creates an “Open edX named release” every six months. The Open edX community, led by the Build Test Release working group, tests the release for two months prior to it being made available to the community. The codebase is also extensively tested by the 2U/edX team, who deploys the code to the edx.org website multiple times a day.

Open edX releases are named alphabetically with botanical tree names.

Latest Open edX Release#

The latest supported release line is Quince, based on code from 2023-10-10.

The next release will be Redwood.

Dates for recent and upcoming releases can be found in the Release Schedule.

All Open edX Releases#

Note that the latest release 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 the Open edX Platform Release Notes.

Every release line (Ginkgo, Hawthorn, etc) has a branch that accumulates changes destined for that release (open-release/ginkgo.master, open-release/hawthorn.master, etc). Periodically, we tag that branch (open-release/hawthorn.1, open-release/hawthorn.2, etc). After a few releases, 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.

If an installation of a tag fails, try the corresponding release line master branch, it may have a fix.

Redwood#

Quince#

Release Name

Release Date

Git Tag

Quince.1

2023-12-11

open-release/quince.1

Quince.2

2024-02-09

open-release/quince.2

Quince.3

2024-04-09

open-release/quince.3

Palm#

Release Name

Release Date

Git Tag

Palm.1

2023-06-14

open-release/palm.1

Palm.2

2023-08-09

open-release/palm.2

Palm.3

2023-10-13

open-release/palm.3

Palm.4

2023-11-16

open-release/palm.4

Olive#

Release Name

Release Date

Git Tag

Olive.1

2022-12-12

open-release/olive.1

Olive.2

2023-02-09

open-release/olive.2

Olive.3

2023-04-11

open-release/olive.3

Olive.4

2023-05-22

open-release/olive.4

Nutmeg#

Release Name

Release Date

Git Tag

Nutmeg.1

2022-06-09

open-release/nutmeg.1

Nutmeg.2

2022-08-08

open-release/nutmeg.2

Nutmeg.3

2022-10-11

open-release/nutmeg.3

Maple#

Release Name

Release Date

Git Tag

Maple.1

2021-12-20

open-release/maple.1

Lilac#

Release Name

Release Date

Git Tag

Lilac.2

2021-08-09

open-release/lilac.2

Lilac.1

2021-06-09

open-release/lilac.1

Koa#

Release Name

Release Date

Git Tag

Koa.3

2021-04-07

open-release/koa.3

Koa.2a

2021-02-10

open-release/koa.2a

Koa.2

2021-02-09

open-release/koa.2

Koa.1

2020-12-09

open-release/koa.1

Juniper#

Release Name

Release Date

Git Tag

Juniper.3

2020-08-25

open-release/juniper.3

Juniper.2

2020-07-13

open-release/juniper.2

Juniper.1

2020-06-09

open-release/juniper.1

Ironwood#

Release Name

Release Date

Git Tag

Ironwood fixes

2019-06-26+

open-release/ironwood.master

Ironwood.2

2019-06-05

open-release/ironwood.2

Ironwood.1

2019-03-21

open-release/ironwood.1

Hawthorn#

  • Code cut date: 2018-07-03

  • Status: unsupported

  • Note: Devstack is now based on Docker.

  • Release Notes

Release Name

Release Date

Git Tag

Hawthorn.2

2018-09-26

open-release/hawthorn.2

Hawthorn.1

2018-08-07

open-release/hawthorn.1

Ginkgo#

A note about Vagrant box files:

  • Ginko and earlier 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.

  • Code cut date: 2017-07-06

  • Status: unsupported

  • Latest: open-release/ginkgo.master

  • Release Notes

Release Name

Release Date

Git Tag

Vagrant Box Files

Ginkgo.2

2017-12-18

open-release/ginkgo.2

  • devstack
    • ginkgo-devstack-2017-07-14 *

    • a7e3fce6d0155cde28e9f3253103f3f66ba3ea54

  • fullstack
    • ginkgo-fullstack-2017-12-14

    • c05fcd63df5fae452f0c8cb84720317449215472

Ginkgo.1

2017-08-14

open-release/ginkgo.1

  • devstack
    • ginkgo-devstack-2017-07-14

    • a7e3fce6d0155cde28e9f3253103f3f66ba3ea54

  • fullstack
    • ginkgo-fullstack-2017-08-14

    • 990d5fdb5bbc7683c158dd99d5732064932c9cdd

Ficus#

  • Code cut date: 2017-01-10

  • Status: unsupported

  • Latest: open-release/ficus.master

  • Release Notes

Release Name

Release Date

Git Tag

Vagrant Box Files

Ficus.4

2017-08-10

open-release/ficus.4

  • devstack
    • ficus-devstack-2017-02-07 *

    • a7fb2200ccdb9f847bee7acd97f5e4e1434776b3

  • fullstack
    • ficus-fullstack-2017-08-10

    • c9f59b27b39339d12fcf008f7c5721c2970a57bd

Ficus.3

2017-04-21

open-release/ficus.3

  • devstack
    • ficus-devstack-2017-02-07 *

    • a7fb2200ccdb9f847bee7acd97f5e4e1434776b3

  • fullstack
    • ficus-fullstack-2017-04-20

    • 64eb0a247d99454bccf0eed7ec49b076cbb9cd69

Ficus.2

2017-03-29

open-release/ficus.2

  • devstack
    • ficus-devstack-2017-02-07 *

    • a7fb2200ccdb9f847bee7acd97f5e4e1434776b3

  • fullstack
    • ficus-fullstack-2017-03-28

    • fc6aa0d3b686c83e38e8c7fa1b1f172fcf7f71c1

Ficus.1

2017-02-23

open-release/ficus.1

  • devstack
    • ficus-devstack-2017-02-07

    • a7fb2200ccdb9f847bee7acd97f5e4e1434776b3

  • fullstack
    • ficus-fullstack-2017-02-15

    • cd6310ffc1e6b374d2c3d59aab5191500f9d5d6f

Eucalyptus#

  • Code cut date: 2016-07-13

  • Status: unsupported

  • Latest: open-release/eucalyptus.master

  • Release Notes

Release Name

Release Date

Git Tag

Vagrant Box Files

Eucalyptus.3

2017-01-10

open-release/eucalyptus.3

  • devstack
    • eucalyptus-devstack-2016-09-01 *

    • a26c8fdbb431279863654161d0145732ee36ed66

  • fullstack
    • eucalyptus-fullstack-2017-01-10

    • 64fd2a6efd656a7170127cccdf4458699ea04978

Eucalyptus.2

2016-09-02

open-release/eucalyptus.2

Eucalyptus.1

2016-08-26

open-release/eucalyptus.1

Dogwood#

  • Code cut date: 2015-12-15

  • Status: unsupported

  • Latest: named-release/dogwood.rc

  • Release Notes

Release Name

Release Date

Git Tag

Vagrant Box Files

Dogwood.3

2016-04-25

named-release/dogwood.3

Dogwood.2

2016-04-14

named-release/dogwood.2

Dogwood.1

2016-03-09

named-release/dogwood.1

Dogwood

2016-02-11

named-release/dogwood

Cypress#

  • Code cut date: 2015-07-07

  • Status: unsupported

  • Latest: named-release/cypress.rc

  • Release Notes

Release Name

Release Date

Git Tag

Vagrant Box Files

Cypress

2015-08-13

named-release/cypress

Birch#

  • Code cut date: 2015-01-29

  • Status: unsupported

  • Latest: named-release/birch.rc

  • Release Notes

Release Name

Release Date

Git Tag

Vagrant Box Files

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#

  • Code cut date: 2014-09-05

  • Status: unsupported

  • Release notes: Not available

Release Name

Release Date

Git Tag

Vagrant Box Files

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@openedx.org. Please do not post the vulnerability to the public.

Feedback#

If you find a problem in the release candidate, please report them to the Build-Test-Release Working Group. You can do so by creating a new issue.