Cate Release Template

Create an issue named "Release {version}" and use this template:

---

• Make sure cate/CHANGES.md is complete
• Make sure cate-desktop/CHANGES.md is complete
• Ensure version number in cate/version.py is ok and PEP440-compatible. Commit and push.
• Ensure version number in cate-desktop/package.json and cate-desktop/app/package.json are ok and SemVer-compatible.
• Ensure APP_CLI_VERSION_RANGE in cate-desktop/src/main/appenv.ts is ok and node-semver-compatible. Commit and push.
• Smoke-test Cate CLI and Cate Desktop build from local sources.
• Ensure builds on Travis and AppVeyor are green. See Cate Automation.
• Adapt version number refs in cate-conda, commit + push. As commit message use "{version}, b{build-no}". This will deploy cate-cli to Anaconda Cloud, channel ccitools.
• Once cate-cli is available in Anaconda channel, adapt version number refs in cate-installer, commit + push. As commit message use "{version}, b{build-no}". This will copy installers to ftp.brockmann-consult.de, user ccitbx.
• Download installers and smoke-test on Windows, Mac OS X and Linux.
• Draft a new release on cate/releases. Reuse name, tag, and text of previous release as template. Tag name must be "v{version}".
• Upload installers to draft release.
• Release.
• Adapt docs to current version number in web page cci-tools.github.io
• Update Cate docs in cate/doc to [match this release][1] with special care on user_manual/um_setup.rst.
• Ensure that all operations listed in cate/ops/__init__.py are referenced in doc/source/api_reference.rst
• Check in the build logs for RTD that the doc builds are ok, see also Cate Automation.

---

[1]: Note that it is ok to change cate/doc after the release as it should refer to the latest, recent cate release. Any cate/doc updates that refer to not-yet-released changes should be made on an extra doc branch.