Skip to content

Latest commit

 

History

History
31 lines (30 loc) · 2.89 KB

how-to-release.md

File metadata and controls

31 lines (30 loc) · 2.89 KB

How to Release

  • Prepare release PR:
    • Pull the changes in the helm-charts submodule folder to get the latest main.
      • cd helm-charts
      • git submodule update --init - if submodule was not initialised before
      • git pull origin main
    • Update any changing versions in release.json.
      • operator - always when doing a release
      • version-upgrade-hook - whenever we make changes in the versionhook files
      • readiness-probe - whenever we make changes in the readiness files
      • agent - newest version available in ops-manager conf-hosted.properties file under automation.agent.version
      • agent-tools-version - newest version available in ops-manager conf-hosted.properties file under mongotools.version
    • Ensure that the release notes are up to date for this release.
      • all merged PRs have a covered entry in the release notes. For example, you can use git log v0.11.0..HEAD --reverse --oneline to get the list of commits after previous release
    • Run python scripts/ci/update_release.py to update the relevant yaml manifests.
      • use venv and then python3 -m pip install -r requirements.txt
    • Copy CRD`s to Helm Chart
      • cp config/crd/bases/mongodbcommunity.mongodb.com_mongodbcommunity.yaml helm-charts/charts/community-operator-crds/templates/mongodbcommunity.mongodb.com_mongodbcommunity.yaml
      • commit changes to the helm-charts submodule and create a PR against it (similar to this one).
      • do not merge helm-charts PR until release PR is merged and the images are pushed to quay.io.
      • do not commit the submodule change in the release pr of the community repository.
    • Commit all changes (except for the submodule change)
    • Create a PR with the title Release MongoDB Kubernetes Operator v<operator-version> (the title must match this pattern).
    • Wait for the tests to pass and merge the PR.
      • Upon approval, all new images for this release will be built and released, and a GitHub release draft will be created.
        • Dockerfiles for mongodb-kubernetes-operator and mongodb-agent will be uploaded to S3 to be used by daily rebuild process in the enterprise repo.
      • Review and publish the new GitHub release draft, that was prepared
    • Merge helm-charts PR and update submodule to the latest commit on main branch.
    • Create a new PR with only bump to the helm-chart submodule, similar to this. The commit here should match the master commit in the helm-charts repository.
    • Add the new released operator version to the enterprise release.json file.