Update RELEASE.md #121
Update RELEASE.md #121
Conversation
k8s-ci-robot
added
the
cncf-cla: yes
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: nojnhuh The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
k8s-ci-robot
added
approved
| SHA digests and tags of the new artifacts from the staging repo | ||
| - Example PR: https://github.com/kubernetes/k8s.io/pull/7871 | ||
| 1. The artifacts are verified to be available from registry.k8s.io | ||
| 1. The artifacts are verified to be available from registry.k8s.io: |
There was a problem hiding this comment.
I also suggested we test the promoted artifacts after this step, but there isn't an easy way to do that without hacking around the existing scripts to run the e2e tests. I'll open an issue to track enabling that.
| The issue should describe if one or both of the container image and Helm | ||
| chart should be released. | ||
| - Example issue: https://github.com/kubernetes-sigs/dra-example-driver/issues/119 | ||
| 1. At least two of the [OWNERS](OWNERS) must agree to move forward with this |
There was a problem hiding this comment.
Would it make sense to explain how they must agree and if release PR author is counted?
There was a problem hiding this comment.
I don't think we need to specify any formal mechanism here. The only thing this is trying to prevent is any single person from pushing through a release totally by themselves.
|
/hold for squash |
k8s-ci-robot
added
do-not-merge/hold
|
/lgtm |
k8s-ci-robot
added
the
lgtm
nojnhuh
force-pushed
the
update-release-guide
branch
from
8a6806f to
a02b3e6
Compare
k8s-ci-robot
removed
the
lgtm
|
Squashed! @bart0sh one more quick lgtm would be great, thanks! /hold cancel |
k8s-ci-robot
removed
the
do-not-merge/hold
|
/lgtm |
k8s-ci-robot
added
the
lgtm
3 participants
This PR incorporates feedback from @bart0sh as we cut the v0.2.0 release.
Real-time discussion as we were cutting the release for posterity: https://kubernetes.slack.com/archives/C0409NGC1TK/p1756330903622829