-
Notifications
You must be signed in to change notification settings - Fork 688
Release Process (1.14.z)
Luke Shumaker edited this page Jun 10, 2022
·
7 revisions
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.
- 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
, andossVersion
, WITH-rc.N
) - edit
charts/ambassador/values.yaml
(image.ossTag
andimage.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.
- wait for CI to run on the PR; we need the Docker image it spits out
- create+push a
v1.14.4-rc.0
(andchart/v6.9.5-rc.0
?) Git tag
- 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
andmake go-mod-tidy
andgo 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.
- now that an Edge Stack RC image has been pushed, go restart Emissary's failing
oss-dev-chart
CI job.
TODO
Then GA is that all over again (but obviously without -rc.N
anywhere).