Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update the release process doc for conformance tests #852

Merged
merged 1 commit into from
Jul 12, 2023
Merged

Update the release process doc for conformance tests #852

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 5 additions & 2 deletions docs/release-process.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -32,10 +32,13 @@ To create a new release, follow these steps:
4. If a problem is found, prepare a fix PR, merge it into the main branch and return to the previous step.
5. Create a release branch with a name that follows the `release-X.Y` format.
6. Prepare and merge a PR into the release branch to update the repo files for the release:
1. Update the tag of NKG container images used in the installation manifests and docs to `X.Y.Z`.
1. Update the tag of NKG container images used in the installation manifests (both the
[deployment manifest](../deploy/manifests/deployment.yaml) and the
[provisioner manifest](../conformance/provisioner/provisioner.yaml)) and docs to `X.Y.Z`.
2. Ensure that the `imagePullPolicy` is `IfNotPresent` in the installation manifests.
3. Modify any `git clone` instructions to use `vX.Y.Z` tag.
4. Adjust the `VERSION` variable in the [Makefile](../Makefile) to `X.Y.Z`.
4. Adjust the `VERSION` variable in the [Makefile](../Makefile) and the `NKG_TAG` in the
[conformance tests Makefile](../conformance/Makefile) to `X.Y.Z`.
5. Update the [README](../README.md) to include information about the release.
6. Update the [changelog](../CHANGELOG.md). The changelog includes only important (from the user perspective)
changes to NKG. This is in contrast with the autogenerated full changelog, which is created in the next step. Use
Expand Down
Loading