Release check lit

Before the release

• Check all module PV GUIs (right category?, right layout?)

• Build and double-check mkdocs: all examples do indeed link to all the TTK modules they used (core/vtk), and reciprocally

• Update module white list for Kitware (ParaView integration) based on CI tests (ttk-data/states/whiteList.sh)

• Update ChangeLog

• Update LICENSE

• Update splash screen

• Update versioning

  • paraview/patch
  • CMakeLists.txt
  • core/base/common/Debug.h

• switch developer flags to default values and BUILD:

  • Build mode: Release
  • TTK_ENABLE_KAMIKAZE ON
  • TTK_ENABLE_DOUBLE_TEMPLATING ON

• Build and test doxygen documentation

• Run builtin examples

• Run every example from ttk-data (pvsm and py)

• Run every example from examples/

• tag release

  • git tag -a 0.9.9 -m "TTK 0.9.9"
  • git push --tags
  • same for ttk-data

• PR from dev to stable

• switch back developer flags to developer values:

  • Build mode: Debug
  • TTK_ENABLE_KAMIKAZE OFF
  • TTK_ENABLE_DOUBLE_TEMPLATING OFF

After the release

• Update https://topology-tool-kit.github.io/installation.html
• Update https://topology-tool-kit.github.io/downloads.html
• Update https://topology-tool-kit.github.io/tutorials.html
• Update https://topology-tool-kit.github.io/doc/html/index.html

ccache in CI (optional)

• if the CI takes too long to build ttk (this can happen after editing a core header file), trigger a new cache.
• delete the previous ccache pre-release in github (https://github.com/topology-tool-kit/ttk/releases)
• git tag -f ccache && git push -f ttk-public ccache

For 0.9.9 only

• Deploy azure on the stable branch