Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The documentation process page (Open edX Release Documentation and Versioning) has things to do, including updating the help links in edx-platform.  Be sure to do this before release day, so that changes have time to pass edx-platform CI gates.

Make a release or release candidate

Releases and release candidates are tags marking specific versions of all the repos, packaged as a box file.  Take care with the steps to create and tag these.  It's surprising, but you have to edit files to refer to the tags before you can create the tag.

...

  • Add the new box, and a new row in the table if need be. Be careful when editing URLs that you change both the text and the link.
  • Add the SHA1 hash of the box file, from "shasum package.box"
  • Click the torrent URLs to make sure they work. If they 404, then the file doesn't exist, or has the wrong permissions.  If you get "The s3.amazonaws.com page isn’t working. s3.amazonaws.com didn’t send any data," then click it again until it gives you a file of about 220Kb.  Amazon takes a while to get the torrent file going.

Testing

This section is a bit disorganized. Use judiciously.

Test upgrade to master (??)

Create a devstack VM and a fullstack VM from the previous Open edX release:

...

If it fails, work with devops to figure out what's going wrong and how to fix it. Note that the above ansible command seems to only work for fullstack, since devstack doesn't have a /edx/app/edx_ansible/server-vars.yml file. Still trying to figure out how to test this with devstack.

Test/Update the upgrade.sh script

The upgrade script is in the configuration repo at utils/vagrant/upgrade.sh.  Make a branch from open-release/zebrawood/master for bringing upgrade.sh up to date, let's call it you/open-upgrade.  Check on all the things from the Open edX release page for collecting devops details about this release, for example: Eucalyptus.  Each of them should be accounted for in the upgrade.sh script or the playbooks it invokes.

...

  1. Revert to the pristine snapshot.
  2. Bring up the box and ssh into it.
  3. Download the upgrade.sh script and run it:

    Code Block
    export CONFIGURATION_TARGET=you/open-upgrade
    curl -OL https://raw.github.com/edx/configuration/$CONFIGURATION_TARGET/util/vagrant/upgrade.sh
    bash upgrade.sh -c devstack -t open-release/zebrawood.master       # Change devstack to fullstack when testing fullstack.


  4. This should upgrade the box from Yucca to Zebrawood. If it doesn't, fix the problem, push to the upgrade working branch, and try again.
  5. Once it works, merge the you/open-upgrade branch to open-release/zebrawood.master

Test clean installation

Release Test Process

Test the native installation

Native Open edX Ubuntu 16.04 64 bit Installation

...