Skip to content

release_guide.rst

Latest commit

 

History

History
192 lines (120 loc) · 6.3 KB

release_guide.rst

File metadata and controls

192 lines (120 loc) · 6.3 KB

Release Guide

This guide documents the dask-image release process. It is based on the napari release guide created by Kira Evans.

This guide is primarily intended for core developers of dask-image. They will need to have a PyPI account with upload permissions to the dask-image package. They will also need permissions to merge pull requests in the dask-image conda-forge feedstock repository: https://github.com/conda-forge/dask-image-feedstock.

You will also need these additional release dependencies to complete the release process:

pip install PyGithub>=1.44.1 twine>=3.1.1 tqdm

Set PyPI password as GitHub secret

The dask/dask-image repository must have a PyPI API token as a GitHub secret.

This likely has been done already, but if it has not, follow this guide to gain a token and this other guide to add it as a secret.

Determining the new version number

We use calendar versioning (CalVer) for dask-image. This means version numbers have the format YYYY.MM.X. Here, YYYY indicates the year, MM indicates the month, and X is an integer counter beginning at zero (to distinguish between cases where multiple releases were made in the same month).

Versioneer then determines the exact version from the latest git tag beginning with v. So our git tags will have the format vYYYY.MM.X.

So for example, a git tag "v2030.01.0" will be the first release made in the month of January, in the year 2030.

Generate the release notes

The release notes contain a list of merges, contributors, and reviewers.

  1. Create a GH_TOKEN environment variable on your computer.

    On Linux/Mac:

    export GH_TOKEN=<your-gh-api-token>

    On Windows:

    set GH_TOKEN <your-gh-api-token>

    If you don't already have a personal GitHub API token, you can create one from the developer settings of your GitHub account: https://github.com/settings/tokens

2. Run the python script to generate the release notes, including all changes since the last tagged release.

Note: The PyGithub package must be installed to run this script (https://github.com/PyGithub/PyGithub)

Call the script like this:

python docs/release/generate_release_notes.py  <last-version-tag> main --version <new-version-number>

An example:

python docs/release/generate_release_notes.py  v2021.05.24 main --version 2021.06.03

See help for this script with:

python docs/release/generate_release_notes.py -h
  1. Scan the PR titles for highlights, deprecations, API changes, and bugfixes, and mention these in the relevant sections of the notes. Try to present the information in an expressive way by mentioning the affected functions, elaborating on the changes and their consequences. If possible, organize semantically close PRs in groups.
  2. Copy your edited release notes into the file HISTORY.rst.
  3. Make and merge a PR with the release notes before moving onto the next steps.

Create the release candidate

Go to the dask-image releases page: https://github.com/dask/dask-image/releases

Click the "Draft Release" button to create a new release candidate.

  • Both the tag version and release title should have the format vYYYY.MM.Xrc1.
  • Copy-paste the release notes from HISTORY.rst for this release into the description text box.
  • Tick "Set as a pre-release"

Note here how we are using rc for release candidate to create a version of our release we can test before making the real release.

Creating the release will trigger a GitHub actions script, which automatically uploads the release to PyPI.

Testing the release candidate

The release candidate can then be tested with

pip install --pre dask-image

It is recommended that the release candidate is tested in a virtual environment in order to isolate dependencies.

If the release candidate is not what you want, make your changes and repeat the process from the beginning but incrementing the number after rc (e.g. vYYYY.MM.Xrc1).

Once you are satisfied with the release candidate it is time to generate the actual release.

Generating the actual release

To generate the actual release you will now repeat the processes above but now - dropping the rc suffix from the version number. - ticking "Set as the latest release"

This will automatically upload the release to PyPI, and will also automatically begin the process to release the new version on conda-forge.

Releasing on conda-forge

It usually takes about an hour or so for the conda-forge bot regro-cf-autotick-bot to see that there is a new release available on PyPI, and open a pull request in the dask-image conda-forge feedstock here: https://github.com/conda-forge/dask-image-feedstock

Note: the conda-forge bot will not open a PR for any of the release candidates, only for the final release. Only one PR is opened for

As an alternative to waiting for the conda-forge bot to notice the new release, you can submit a new dask-image feedstock issue indicating @conda-forge-admin, please update version in the issue title. This will trigger <https://conda-forge.org/docs/maintainer/infrastructure.html#conda-forge-admin-please-update-version>`_ the bot to check for new versions.

Before merging the pull request, first you should check:

  • That all the tests have passed on CI for this pull request
  • If any dependencies were changed, and should be updated by commiting changes to recipe/meta.yaml to the pull request

Once that all looks good you can merge the pull request, and the newest version of dask-image will automatically be made available on conda-forge. We're finished!