Release Process (1.14.z)

The release/v1.14 maintenance branch is substantially behind the current release process.

Here's the skinny of what you have to do for 1.14.z:

Because of the shared Helm chart, Emissary 1.14 and Edge Stack 1.14 releases need to be done in lockstep. It aught to be possible to do one without the other by only changing one set of values in Chart.yaml/values.yaml, but if you're intending to do a release of both, then this process gets interwoven.

RC

Prepare the Emissary RC

• edit charts/ambassador/README.md (image.tag in variables table, no -rc.N)
• edit charts/ambassador/CHANGELOG.md (WITH -rc.N)
• edit charts/ambassador/Chart.yaml (version, appVersion, and ossVersion, WITH -rc.N)
• edit charts/ambassador/values.yaml (image.ossTag and image.aesTag, WITH -rc.N)
• edit docs/yaml/versions.yml (version, no -rc.N)
• run make generate
• commit any changes
• Push the changes, file a PR. It is expected that at this point the oss-dev-chart CI job will fail.

Promote Emissary to RC

• wait for CI to run on the PR; we need the Docker image it spits out
• create+push a v1.14.4-rc.0 (and chart/v6.9.5-rc.0?) Git tag

Prepare the Edge Stack RC

• edit Makefile (EMISSARY_BASE_TAG, WITH -rc.N)
• edit aes-example-plugins/Makefile (AES_VERSION, NO -rc.N)
• edit go.mod (github.com/datawire/ambassador, WITH -rc.N)
• run make generate and make go-mod-tidy and go mod tidy a couple of times, IDK.
• commit any changes
• Push the changes, file a PR. Some of the CI jobs for the PR are expected to fail (in particular: test-chart)
• wait for CircleCI to promote the image to an RC.

TODO: there's more

GA

Then GA is that all over again (but obviously without -rc.N anywhere).