3.3.0 (& chart 4.0.0) Release Checklist

[artntek]

Release checklist

Metacat App Release 3.3.0
Helm chart 4.0.0 (because of significant change in indexer RMQ operator requirements)

• Create a branch named feature-<issueNum>-<releaseVer>-release-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!
  • 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
• PR & merge develop -> main
• (Linux VM) build and push docker image
• (Mac) package and push helm chart
• (Mac) build binary packages & upload to knb site
• Tag the release; look up the <commit-sha> from git log, then:

  git tag x.x.x <commit-sha>
  git tag chart-x.x.x <commit-sha>
  git push --tags    ## IMPORTANT - DON'T FORGET THIS!

• Add to GH Releases page (& link to binaries that are on KNB site - don't upload to GH!)
• Send email
• announce on Slack