From b55ea775838accc78ca55947316188207cfc65ba Mon Sep 17 00:00:00 2001 From: Pierre Tessier Date: Sat, 1 Mar 2025 09:05:44 -0500 Subject: [PATCH] [chore] update release process (#2097) --- CONTRIBUTING.md | 10 +++++++--- README.md | 2 +- 2 files changed, 8 insertions(+), 4 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 94a4816182..866205e07e 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -296,13 +296,17 @@ Maintainers can create a new release when desired by following these steps. notes. 3. After images for the new release are built and published, create a new Pull Request that updates the `CHANGELOG.md` with the new version leaving the - `Unreleased` section for the next release. + `Unreleased` section for the next release. Merge the Pull Request. 4. Create a new Pull Request to update the deployment of the demo in the [OpenTelemetry Helm Charts](https://github.com/open-telemetry/opentelemetry-helm-charts) repo. + Merge the Pull Request. 5. After the Helm chart is released, create a new Pull Request which updates the - Demo's Kubernetes manifest by running `make generate-kubernetes-manifests` - and committing the changes. + Demo's Kubernetes manifest by running `make generate-kubernetes-manifests`. + Merge the Pull Request. +6. Create a new Tag for the _new_ version with a suffix of `-k8s`. This tag + will be used to deploy the new version of the demo to Kubernetes using the + supplied manifests. [docs]: https://opentelemetry.io/docs/demo/ diff --git a/README.md b/README.md index 1e5dad521e..560fb56b2a 100644 --- a/README.md +++ b/README.md @@ -73,7 +73,7 @@ keeping it up to date for you. To get involved with the project see our [CONTRIBUTING](CONTRIBUTING.md) documentation. Our [SIG Calls](CONTRIBUTING.md#join-a-sig-call) are every other -Monday at 8:30 AM PST and anyone is welcome. +Wednesday at 8:30 AM PST and anyone is welcome. ## Project leadership