Page Comparison

...

Clone the configuration repo and build Vagrant boxes from scratch for fullstack and possibly devstack. Make sure to use the "base" version, not the "release" version.

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

...

Announce to the community

Send an email: for rc's, to openedx-ops. For real releases, to edx-code, openedx-ops, and openedx-announce. 

Change the topic line in the #ops channel in Slack.

Things we used to do, rethink:

• For Birch, we did both an email to edx-code and a post to the engineering blog. You should also let everyone at edX know that the Open edX release candidate branch has been cut, and they should notify you of all bugfixes merged to master for the next few weeks.
• You should also create a Confluence page summarizing the status of the release candidate branch. Here's the one we used for Birch.

Collect bugfixes, create new release candidates

...