Skip to content

Latest commit

 

History

History
86 lines (67 loc) · 4.33 KB

RELEASE.md

File metadata and controls

86 lines (67 loc) · 4.33 KB
Raw

Release Process

Overview

The Network Policy API project is has the following two main release components:

  • Kubernetes Custom Resource Definitions (CRDs)
  • Corresponding Go bindings for the API (sigs.k8s.io/network-policy-api Go package)

This repository is the home for both of the above components.

Versioning strategy

The versioning strategy for this project is covered in detail in the release documentation.

Adapted with 💙 from the gateway api project release documentation

Releasing a new version

Writing a Changelog

To simplify release notes generation, we recommend using the Kubernetes release notes generator:

go install k8s.io/release/cmd/release-notes@latest
export GITHUB_TOKEN=your_token_here
release-notes --start-sha EXAMPLE_COMMIT --end-sha EXAMPLE_COMMIT --branch main --repo network-policy-api --org kubernetes-sigs

This output will likely need to be reorganized and cleaned up a bit, but it provides a good starting point. Once you're satisfied with the changelog, create a PR. This must go through the regular PR review process and get merged into the main branch. Approval of the PR indicates community consensus for a new release.

Release Steps

The following steps must be done by one of the network-policy API maintainers:

For a PATCH release:

  • Create a new branch in your fork named something like <githubuser>/release-x.x.x. Use the new branch in the upcoming steps.
  • Use git to cherry-pick all relevant PRs into your branch.
  • Update pkg/generator/main.go with the new semver tag and any updates to the API review URL.
  • Create a pull request of the <githubuser>/release-x.x.x branch into the release-x.x branch upstream (which should already exist since this is a patch release). Add a hold on this PR waiting for at least one maintainer/codeowner to provide a lgtm.
  • Verify the CI tests pass and merge the PR into release-x.x.
  • Create a tag using the HEAD of the release-x.x branch. This can be done using the git CLI or Github's release page.
  • Run the make build-install-yaml command which will generate install files in the release/ directory. Attach these files to the Github release.
  • Update the website files to point links and examples to the new release (simply grep for previous version).
  • Write a changelog for the new release in the changelog readme.
  • Make the new-release from the releases page with the new changelog and attach the install.yaml.

For a MAJOR or MINOR release:

  • Cut a release-major.minor branch that we can tag things in as needed.
  • Check out the release-major.minor release branch locally.
  • Update pkg/generator/main.go with the new semver tag and any updates to the API review URL.
  • Verify the CI tests pass before continuing.
  • Create a tag using the HEAD of the release-x.x branch. This can be done using the git CLI or Github's release page.
  • Run the make build-install-yaml command which will generate install files in the release/ directory. Attach these files to the Github release.
  • Update the website files to point links and examples to the new release (simply grep for previous version).
  • Write a changelog for the new release in the changelog readme.
  • Make the new-release from the releases page with the new changelog and attach the install.yaml.

For an RC release:

  • Update pkg/generator/main.go with the new semver tag and any updates to the API review URL.
  • Include the changelog update in this PR.
  • Merge the update PR.
  • Tag the release using the commit on main where the changelog update merged. This can be done using the git CLI or Github's release page.
  • Run the make build-install-yaml command which will generate install files in the release/ directory.
  • Attach these files to the Github release.