Metacat 3.5.1 (chart-4.3.2) Release Checklist

[artntek]

Release checklist

• Create a branch named task-2363-release-3.5.1-prep, and do the following:

  • pom.xml: Update <version>x.x.x</version>

  • Chart.yaml: Update chart version and appVersion

  • Grep codebase for previous release number, just in case

  • RELEASE-NOTES.md:

    • Update for new app & chart versions

    • DON'T FORGET TO SET CORRECT RELEASE DATE! (2 places):

      ```
      Release Notes for Metacat 3.5.1
      **Release date: @TODO **
      
      Release Notes for Helm Chart 4.3.2
      **Release date: @TODO **
      ```
      

  • pom.xml: Update <metacat_common_version>x.x.x</metacat_common_version>

  • metacat-common/pom.xml: Update <version>x.x.x</version>

  • metacat-index/pom.xml: Update <version>x.x.x</version> and <metacat_common_version>x.x.x</metacat_common_version>

  • build.properties:

    • update metacat.version and metacatui.tag

  • SQL:

    • Add a new db upgrade script for this version
    • Modify the version in loaddtdschema-postgres.sql

  • README.md:

    • Update release number
    • Add new DOI for this release (2 places)

  • metacat.properties:

    • Update the version
    • Add a new db upgrade script property

  • Draft release email

  • PR & merge release prep branch to develop - PULL REQUEST IS HERE

• PR & merge develop -> main
• Merge main back to develop

  git checkout develop; git merge main --ff-only
  git push

• build and push docker image
• package and push helm chart
• build binary packages & upload to knb site
• Tag the release; look up the <commit-sha> from git log, then:

  # Always use annotated tags (-a) for releases
  git tag -a x.x.x <commit-sha> -m "Metacat Release x.x.x"
  git tag -a chart-x.x.x <commit-sha> -m "Metacat Helm Chart x.x.x"
  git push --tags    ## IMPORTANT - DON'T FORGET THIS!

• Add the metadata for the reserved DOI and publish it with the correct softwareheritage url
• Add to GH Releases page (& link to binaries that are on KNB site - don't upload to GH!) - DRAFT RELEASE ANNOUNCEMENT IS HERE
• Send email (EMAIL TEMPLATE IS HERE)
• announce on Slack