Skip to content

Release Checklist

Marcel Wallschläger edited this page Mar 8, 2024 · 16 revisions

Checklist to create a new release

I) Create a final release branch like: $release with a PR for a new release. The final PR should contain:

  1. Update Chart.yaml version entry to the new version and edit description writing down geonode/geoserver target versions
  2. Add new version to the version overview table docs/list-of-release-versions.md
  3. Update Badge in /README.md
  4. Go through all docs/ files and check if they are still up to date, with the changes comming to this release, if not UPDATE DOCS
  5. update /charts/geonode/README.md (this happens automatically by the pre-commit)
  6. copy /README.md to docs/index.md

II) After merge this commit:

  1. check that github actions Relase-Charts and pages-build-deployment finished successfully

III) When everything looks good so far:

  1. check if release is created geonode-k8s-1.0.2
  • maybe edit release notes
  1. check if new version appears in helm repo with:
  • add helm repo with helm repo add geonode-k8s https://zalf-rdm.github.io/geonode-k8s/
  • if you already have added the repo before run a helm repo update to update repo
  • then check for available version with helm search repo https://zalf-rdm.github.io/geonode-k8s/ --versions output must be something like:
NAME                    CHART VERSION   APP VERSION     DESCRIPTION                                       
geonode/geonode-k8s     4.1.0                           Helm Chart for Geonode a web-based application ...
geonode/geonode-k8s     1.0.0                           Helm Chart for Geonode a web-based application ...
  1. check that the new version appears on artifacthub
Clone this wiki locally