Skip to content

Latest commit

 

History

History
34 lines (23 loc) · 935 Bytes

RELEASE_PROCEDURE.md

File metadata and controls

34 lines (23 loc) · 935 Bytes
Raw

Blaze Release Procedure

This document describes the steps to follow to release a new version of Blaze.

  1. Update version numbers in the following locations:
  • /setup.py, in the setup(...) call.
  • /README.md where it mentions the current release.
  • /blaze/init.py

  1. Confirm the dependencies and their version numbers in /docs/installing /requirements.txt

    In particular, blz, dynd-python, etc will typically be released concurrently with blaze, so they need to be updated to match.

  2. Update the release notes /docs/source/releases.rst

  3. Build and update the documentation in gh-pages.

  4. Verify build is working on all platforms. The jenkins builder internal to Continuum can assist with this.

  5. Tag the release version.

  6. Release email to blaze-dev@continuum.io.

  7. Update this release procedure document to reflect what needed to be done for the release.