Page Comparison

...

To make the vagrant boxes, but not yet mark the release, we'll make a test branch.  The branch should use your personal prefix ("you/"), and be named for the release you are working on, but with an additional .n suffix.  Don't use the full release name, or people will find the branch and think it is a release:

tag_release --doit --branch --skip-invalid --override-ref open-release/zebrawood.master you/test/zebrawoodz.1rc1.1

The .1 suffix is so that you can make a .2 if something needs to be fixed.

...

export OPENEDX_RELEASE=you/test/zebrawoodz.1rc1.1
git clone https://github.com/edx/configuration.git
cd configuration
git pull; git checkout $OPENEDX_RELEASE
python -m virtualenv -p python2.7 venv
. venv/bin/activate
make requirements
cd vagrant/base/fullstack     # or devstack
vagrant up

...

tag_release --doit --tag --skip-invalid --override-ref you/test/zebrawoodz.1rc1.1 open-release/zebrawood.1rc1		# for release candidate
# or:
tag_release --doit --tag --skip-invalid --override-ref you/test/zebrawoodz.1.1 open-release/zebrawood.1				# for release

It's tempting to do this before creating the Vagrant box. In practice, the first time you create the Vagrant box, it will probably fail, and you'll need to make some fixes. Therefore, it's better to wait until everything works properly before you make the tag.

You can delete the test branches you made once the release is marked:

tag_release --doit --branch --skip-invalid --reverse  you/test/z.1rc1.1

Update box directory

Update the wiki page that lists the boxes: Open edX Releases.

...