Release Process rauc-hawkbit-updater
====================================

Preparation
-----------
- check for GitHub milestone to be completed
  - review & merge open PRs if necessary
- update CHANGES.rst
- update version in docs/conf.py and meson.build
- create preparation PR, merge PR

Release
-------
- update release date in CHANGES.rst and commit
- create signed git tag::

    git tag -m 'release v1.0' -s -u 925F79DAA74AF221 v1.0

- create release tar archive::

    meson setup build
    ninja -C build dist

  The resulting archive will be placed at build/meson-dist/rauc-hawkbit-updater-<version>.tar.xz

- sign (and verify) source archive::

    gpg --detach-sign -u 925F79DAA74AF221 --armor build/meson-dist/rauc-hawkbit-updater-<version>.tar.xz
    gpg --verify build/meson-dist/rauc-hawkbit-updater-<version>.tar.xz.asc

- push master commit (if necessary)
- push signed git tag
- Creating GitHub release
  - Start creating release from git tag
  - upload source archive and signature
  - add release text using CHANGES::
    
      pandoc -f rst -t markdown_github CHANGES.rst

  - Submit release button
