Add instructions for the release process #346
Conversation
k8s-ci-robot
added
the
cncf-cla: yes
k8s-ci-robot
added
the
approved
k8s-ci-robot
added
the
size/M
docs/RELEASE.md
Outdated
|
|
||
| Bumping a minor version after releasing a new feature: | ||
| ``` | ||
| v0.4.5 -> v0.5.0-alpha.0 |
There was a problem hiding this comment.
Can we make these examples 1.x.y? Technically v0.x.y are unstable and can have breaking changes at any time.
Separately, its probably worth cutting a v1.0.0 since we're pretty stable
There was a problem hiding this comment.
That's fair on both points. We can probably work towards a 1.0 but should have a bit of an issue triage, and make any necessary fixes before cutting it.
docs/RELEASE.md
Outdated
|
|
||
| ## Check the release on github | ||
|
|
||
| Look at the release that was just published and validate that the release has the appropriate binaries (compare to a previous release). Check the ECR registry to make sure that the images were published. Finally, edit the release text to match previous releases, by copying the changelog text and adding the container image links. |
There was a problem hiding this comment.
Can we document what the proper release binaries are?
Co-authored-by: Micah Hausler <micahhausler@users.noreply.github.com>
Co-authored-by: Micah Hausler <micahhausler@users.noreply.github.com>
k8s-ci-robot
added
size/L
k8s-ci-robot
added
the
lgtm
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: micahhausler, nckturner The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
./hack/changelog.pyto prepend the new changelog to the beginning of the existing changelog with the correct formatting.