Skip to content

releasing.md

Latest commit

 

History

History
31 lines (29 loc) · 1.43 KB

releasing.md

File metadata and controls

31 lines (29 loc) · 1.43 KB
Raw

Releasing Taskwarrior

To release Taskwarrior, follow this process:

  • Examine the changes since the last version, and update src/commands/CmdNews.cpp accordingly. There are instructions at the top of the file. This is typically only required for minor and major versions.
  • Create a release PR
    • Update version in CMakeLists.txt
    • Update Changelog
    • get this merged
  • On develop after that PR merges, create a release tarball:
    • git clone . release-tarball
    • cd release-tarball/
    • cmake -S. -Bbuild
    • make -Cbuild package_source
    • copy build/task-*.tar.gz elsewhere and delete the release-tarball dir
    • NOTE: older releases had a test-*.tar.gz but it's unclear how to generate this
  • Update stable to the released commit and push upstream
  • Tag the commit as vX.Y.Z and push the tag upstream
  • Find the tag under https://github.com/GothenburgBitFactory/taskwarrior/tags and create a release from it
    • Give it a clever title if you can think of one; refer to previous releases
    • Include the tarball from earlier
    • Publish the release
  • Update https://github.com/GothenburgBitFactory/tw.org
    • Run bin/tw-release vX.Y.Z in that repository. It downloads the tarball from the published GitHub release and updates the relevant files accordingly
    • Create a PR Update Taskwarrior to vX.Y.Z from those changes
  • Update various things, in a new PR:
    • cargo update
    • git submodule update --remote --merge