Skip to content

Latest commit

 

History

History
112 lines (69 loc) · 3.03 KB

RELEASING.rst

File metadata and controls

112 lines (69 loc) · 3.03 KB
Raw

Releasing a version

Preliminaries

  • Make sure that RELEASE_NOTES.md and ANNOUNCE.md are up to date with the latest news in the release.

  • Check that __version__ symbol in caterva2/__init__.py contains the correct info.

  • Commit the changes with:

    $ git commit -a -m "Getting ready for release X.Y.Z"
$ git push

Testing

Follow the steps in README-DEVELOPERS.md file for locally creating and installing the wheel, then test it:

$ python -m pip install -e ".[tests,hdf5]"
$ cd ..   # to avoid using the source code
$ python -m caterva2.tests -v
$ cd -

Check that the examples in docstrings are up to date. You will need to register a user in https://cat2.cloud/demo/ with username '[email protected]' and password 'foo'. Then, copy the content of caterva2-standalone.sample.toml to caterva2.toml and run the following commands:

$ rm -r _caterva2/
$ cat2adduser [email protected] foo -S
$ CATERVA2_SECRET="123" cat2sub
$ python -m doctest  caterva2/api.py
$ python -m doctest  caterva2/api_utils.py

If the tests pass, you are ready to release.

Check documentation

Check that the README.md and README-DEVELOPERS.md are consistent with this new release.

Tagging and releasing

  • Create a tag X.Y.Z from main. Use the next message:

    $ git tag -a vX.Y.Z -m "Tagging version X.Y.Z"

  • Push the tag to the github repo:

    $ git push --tags

  • If you happen to have to delete the tag, such as artifacts demonstrates a fault, first delete it locally:

    $ git tag --delete vX.Y.Z

    and then remotely on Github:

    $ git push --delete origin vX.Y.Z

  • Create a new release by visiting https://github.com/ironArray/Caterva2/releases/new and add the release notes copying them from RELEASE_NOTES.md document.

Check that the release is available at https://pypi.org/project/caterva2/ and test it with:

$ pip install caterva2[tests]
$ python -m caterva2.tests -v
  • Go to Blosc/blogsite repo, then to "Actions", click on the most recent workflow run (at the top of the list), and then click on the "Re-run all jobs" button to regenerate the documentation and check that it has been correctly updated in https://www.blosc.org.

Announcing

  • Send an announcement to the blosc and comp.compression mailing lists. Use the ANNOUNCE.md file as skeleton (likely as the definitive version).
  • Tweet/toot about it from the @Blosc2 account.

Post-release actions

  • Edit __version__ var in caterva2/__init__.py to increment the version to the next minor one (i.e. X.Y.Z --> X.Y.(Z+1).dev0).

  • Create new headers for adding new features in RELEASE_NOTES.md and add this place-holder instead:

    #XXX version-specific blurb XXX#

  • Replace the version-specific blurb of ANNOUNCE.md with this placeholder:

    #XXX version-specific blurb XXX#

  • Commit the changes:

    $ git commit -a -m"Post X.Y.Z release actions done"
$ git push

That's all folks!