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 named releases for Open edX, which are distinct from the weekly deployments to edx.org and have a longer release cycle (on the order of several months between each release). These named releases will be tested both by edX and by the Open edX community, and with each subsequent named release we will include instructions for how to upgrade from the previous named release.
...
| Release Name | Release Date | Git Tag | Vagrant Box Torrents |
|---|---|---|---|
| Aspen | 2014-10-28 | named-release/aspen (previously | |
| Birch (release candidate) | 2015-02-24 | named-release/birch.rc3 | |
| Cypress (future) |
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.
...
The name that you pass to the --name flag should be the same name in the Vagrantfile, and it will generally look something like aspenbirch-devstack-1. Check the Vagrantfile to see exactly what name you need. Once you've downloaded the box file and imported it correctly, you can move on to the standard installation instructions, and Vagrant will automatically know to use the downloaded file rather than trying to download it again. (If Vagrant does try to download the file again, you imported it incorrectly. Check the Vagrantfile to be sure you specified the proper name.)
...