Publish a release

Publication procedure

  • Update merge request template to point to a new changelog wiki page
  • Update CHANGELOG.md to point to new GitLab release
  • Create new web release page with generated artifact names and changelog (convert MR ids to URLs: replace !([0-9][0-9][0-9][0-9]) with [!$1](https://gitlab.opengeosys.org/ogs/ogs/-/merge_requests/$1) and #([0-9][0-9][0-9][0-9]) with [#$1](https://gitlab.opengeosys.org/ogs/ogs/-/issues/$1))
  • Add a link to the (upcoming) Doxygen documentation for this tag in Documentation/mainpage.dox.in (with v-prefix)
  • Update [docs-release]-link in README.md to the new tag (with v-prefix)
  • Add a redirect in scripts/doc/_redirects
  • Create a tag and push
  • A new release is automatically created on GitLab
    • Fill in the release notes from the Wiki
  • Copy release binaries and container images from CI job to Azure OGS storage to a subdirectory containing the tag name at https://ogsstorage.blob.core.windows.net/binaries/ogs6
  • Create a release on GitHub mirror (ufz/ogs)
  • Check if a Zenodo release is automatically issued
  • Issue a scan on Software Heritage Archive
  • Create bugfix branch
    • Create new netlify site (in an empty directory)
      • netlify init
      • # [ENTER]
      • # ogs-doxygen-v[TAG (- separated instead of .)]
    • Create branch from master with name v[TAG] and push
  • Create a discourse announcement post
    • DOI badge
    • Software heritage badge
    • Link to release page on opengeosys.org
    • Link to GitLab release
    • Link to Zenodo release
    • Link to archive on Software Heritage
  • Set milestone on expired issues and merge requests

This article was written by Lars Bilke. If you are missing something or you find an error please let us know. Generated with Hugo 0.96.0. Last revision: May 31, 2022
Commit: [vale] web/content/docs/devguide. 8705d8c  | Edit this page on