doc/design: Update the release documentation #2549
Conversation
timflannagan
force-pushed
the
doc/update-release-documentation
branch
from
0818461 to
d836025
Compare
|
/approve |
|
/lgtm |
| # 0.11.0 is the bumped version. | ||
| git tag -a v0.18.0 -m "Version 0.18.0" | ||
| # v0.20.0 is the bumped version. | ||
| git tag -a v0.20.0 -m "Version 0.20.0" |
There was a problem hiding this comment.
Not necessarily related to the scope of this PR, but... should we sign our tags? (with the --sign flag)
There was a problem hiding this comment.
I don't have any opposition towards doing that. Might be worth bubbling that up to the rest of the team to see if there are any strong objections.
Update release.md now that the repository uses goreleaser to automatically produce draft releases for new tags. Signed-off-by: timflannagan <[email protected]>
timflannagan
force-pushed
the
doc/update-release-documentation
branch
from
d836025 to
f097930
Compare
|
rebased against master to make branch protection happy. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: awgreene, perdasilva, timflannagan 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 |
openshift-ci
bot
added
the
approved
|
Ah - the PR had already been approved by @perdasilva, adding an lgtm. |
|
Force merging as this PR only affects the release documentation and we don't need to continuously run the e2e-tests workflow to get a successful check for this be automatically merged. |
Update release.md now that the repository uses goreleaser to
automatically produce draft releases for new tags.
Signed-off-by: timflannagan [email protected]
Description of the change:
Motivation for the change:
Reviewer Checklist
/doc