Build a version

  1. Pick a release name for the next version
    Releases are versioned using the major.minor.bugfix numbering system.
  2. Update the release notes on the What’s New page
    Check the git log for changes since the last release.
  3. Check that Travis and readthedocs are passing for the latest commit
    Make sure that the tests have finished running!
  4. Tag the branch
    Use the format of datacube-major.minor.bugfix.
  5. Draft a new release on the Datacube GitHub repository
    Include the items added to the release notes in step 2.
  6. Mark the version as released in Jira
    Move any open issues to the next version.
  7. Install the datacube module on raijin
    Follow the instructions on installing the Data Cube module on the Datacube Environment repository, but do not yet make it the default module version.

Marking it stable

Once/if a built version has been tested on Raijin, found to be stable, and the team agrees, we make it the new default stable version.

  1. Merge changes leading up to the release into the stable branch

    This will also update the stable docs

  2. Upload the build to PyPi.

    python sdist bdist_wheel
    twine upload dist/*
  3. Update conda-forge recipe

    Follow the instrucions under Updating datacube-feedstock in the Datcube Feedstock repository

  4. Update the default version on raijin

    Follow the instructions under Update default version in the Datacube Environment repository

  5. Notify the community of the release using the Datacube Central mailing list

    Ask Simon Oliver for the MailChimp details.