|
1 | 1 |
|
2 | 2 | ## How to Release
|
3 | 3 | * Prepare release PR:
|
4 |
| - * Pull the changes in the helm-charts sub module folder to get the latest main. |
5 |
| - * `cd helm-charts && git pull origin main`. |
| 4 | + * Pull the changes in the helm-charts submodule folder to get the latest main. |
| 5 | + * `cd helm-charts` |
| 6 | + * `git submodule update --init` - if submodule was not initialised before |
| 7 | + * `git pull origin main` |
6 | 8 | * Update any changing versions in [release.json](../release.json).
|
| 9 | + * `operator` - always when doing a release |
| 10 | + * `version-upgrade-hook` - whenever we make changes in the [versionhook](../cmd/versionhook) files |
| 11 | + * `readiness-probe` - whenever we make changes in the [readiness](../cmd/readiness) files |
| 12 | + * `agent` - newest version available in `ops-manager` `conf-hosted.properties` file under `automation.agent.version` |
| 13 | + * `agent-tools-version` - newest version available in `ops-manager` `conf-hosted.properties` file under `mongotools.version` |
7 | 14 | * Ensure that [the release notes](./RELEASE_NOTES.md) are up to date for this release.
|
| 15 | + * 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 |
8 | 16 | * Run `python scripts/ci/update_release.py` to update the relevant yaml manifests.
|
9 |
| - * Copy `CRD`s to Helm Chart |
10 |
| - - `cp config/crd/bases/mongodbcommunity.mongodb.com_mongodbcommunity.yaml helm-charts/charts/community-operator-crds/templates/mongodbcommunity.mongodb.com_mongodbcommunity.yaml` |
11 |
| - - commit changes to the [helm-charts submodule](https://github.com/mongodb/helm-charts) and create a PR against it ([similar to this one](https://github.com/mongodb/helm-charts/pull/163)). |
12 |
| - - do not merge helm-charts PR until release PR is merged and the images are pushed to quay.io. |
13 |
| - - do not commit the submodule change in the release pr of the community repository. |
| 17 | + * **use venv and then `python3 -m pip install -r requirements.txt`** |
| 18 | + * Copy ``CRD`s`` to Helm Chart |
| 19 | + * `cp config/crd/bases/mongodbcommunity.mongodb.com_mongodbcommunity.yaml helm-charts/charts/community-operator-crds/templates/mongodbcommunity.mongodb.com_mongodbcommunity.yaml` |
| 20 | + * commit changes to the [helm-charts submodule](https://github.com/mongodb/helm-charts) and create a PR against it ([similar to this one](https://github.com/mongodb/helm-charts/pull/163)). |
| 21 | + * do not merge helm-charts PR until release PR is merged and the images are pushed to quay.io. |
| 22 | + * do not commit the submodule change in the release pr of the community repository. |
14 | 23 | * Commit all changes (except for the submodule change)
|
15 | 24 | * Create a PR with the title `Release MongoDB Kubernetes Operator v<operator-version>` (the title must match this pattern).
|
16 | 25 | * Wait for the tests to pass and merge the PR.
|
|
0 commit comments