Update kpt release process

[ciaranjohnston]

As part of the reinvigoration of the kpt project we are looking to document the release process.

The current release process is described here:

https://github.com/kptdev/kpt/tree/main/release

We should review this in the weekly meeting. One concern is that the currentgoreleaser.yaml is configured to use gcr.io repos:

https://github.com/kptdev/kpt/blob/main/release/tag/goreleaser.yaml

And the release github action is set up to use gcr.io as well:

https://github.com/kptdev/kpt/blob/main/.github/workflows/release.yml

[ciaranjohnston]

Release process should be something like:

• check that dependencies are up to date and that all required release content is in the main branch
• Navigate to https://github.com/kptdev/kpt/releases and select "draft new release"
• Leave the target as "main"
• Create a new tag to match the release version
• • Versioning follows semantic versioning rules
• • Alpha and beta versions are used to make releases before content is fully stabilized
• • • increment the number after "alpha" or "beta" by one when making this type of release - e.g. v1.0.0-beta.58 could come after v1.0.0-beta.57
• Release title should be left blank - it will be auto-filled from the tag
• Click "Generate release notes" to auto-generate the content of the release. Edit this as appropriate to add extra context
• If the release is an alpha or beta release and there is already a stable version available, the "set as a pre-release" check-box should be checked. Otherwise, leave it checked as "set as the latest release"
• Check the "create a discussion for this release" check-box to create an announcement for the release
• Click "publish" and then verify that the github action has run and the artefacts have been produced

[ciaranjohnston]

Created #4239

[ciaranjohnston]

Release process merged