Release workflow

Pre release

  • Tests, check coverage
  • Mypy check
  • Pylint check
  • Translations
  • Update version number in
  • Update database version number in, install SQL and upgrade SQL (if needed)
  • Update model image in application, Sphinx and Redmine
  • Sphinx: update manual, version, check links with uncommenting print in util/ manual()
  • Update changelog, release date
  • Update upgrade and installation notes
  • Prepare newsletter, news


  • Merge develop to main
  • Raise version of develop branch
  • Push to GitHub
  • Upgrade demo versions, if database upgrades:
    pg_dump openatlas_demo > /var/lib/postgresql/openatlas_demo.sql
    pg_dump openatlas_demo_dev > /var/lib/postgresql/openatlas_demo_dev.sql
  • Test demo
  • Post news
  • Upgrade CRAWS and ACDH-CH instances
    • Backup database
    • Check logs
    • Upgrade
    • Send newsletter
    • Raise version at online versions

Post release

  • Update Redmine roadmap
  • Add news item at
  • Git tag
  • Push main and tags to GitHub, GitLab and Bitbucket
  • Update GitHub latest release
  • Update stats in wiki

Updated by Alexander Watzinger 23 days ago · 44 revisions

Also available in: PDF HTML TXT