Skip to content

RELEASING.rst

Latest commit

 

History

History
30 lines (25 loc) · 1.07 KB

RELEASING.rst

File metadata and controls

30 lines (25 loc) · 1.07 KB

jacquard release process

  1. Do sanity checks: verify that the tests and linter pass, locally and on CI.
  2. Update CHANGES:
    • Update the version number
    • Record the release date
    • List major features, minor features, bugfixes, and removals/deprecations.
  3. Update the version number in setup.py
  4. Update the version numbers (version and release) in doc/conf.py.
  5. Create an annotated tag for the version, with the version number as the name.
  6. Push to master, including the tag, which will ship a new release on PyPI.
  7. If pushing a major version, consider creating the stable-<series> branch to which fixes can be backported.

Releasing with aptnik

For those using aptnik to handle their releases, there is an additional step. The CI build process creates a .deb as a build artifact—take the .deb from the build corresponding to the tag, upload it to aptnik, and upgrade on any relevant machines with apt update/ apt upgrade.