github/node-problem-detector
1
0
Fork 0
mirror of https://github.com/kubernetes/node-problem-detector.git synced 2026-08-23 22:26:27 +00:00
Code Issues Packages Projects Releases Wiki Activity

chore: fix misspelling

Browse Source
This commit is contained in:
Yordis Prieto Lazo
2022-12-18 22:58:07 -05:00
parent 2f959a773c
commit 0842910049
16 changed files with 31 additions and 30 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/release_process.md
+4 -4
View File
@@ -14,11 +14,11 @@ itself.
viewing the changes on GitHub ([example:
https://github.com/kubernetes/node-problem-detector/compare/v0.8.6...master](https://github.com/kubernetes/node-problem-detector/compare/v0.8.6...master)).
1. Based on the changes to be included in the release, determine what the next
2. Based on the changes to be included in the release, determine what the next
release number should be. We strive to follow [SemVer](https://semver.org/)
as much as possible.
1. Update [CHANGELOG](https://github.com/kubernetes/node-problem-detector/blob/master/CHANGELOG.md)
3. Update [CHANGELOG](https://github.com/kubernetes/node-problem-detector/blob/master/CHANGELOG.md)
with all significant changes.
## Create release
@@ -31,11 +31,11 @@ body of the release:
release (e.g.
[https://github.com/kubernetes/node-problem-detector/compare/v0.8.5...v0.8.6](https://github.com/kubernetes/node-problem-detector/compare/v0.8.5...v0.8.6)).
1. There is no need to duplicate everything from the CHANGELOG, but include the
2. There is no need to duplicate everything from the CHANGELOG, but include the
most significant things so someone just viewing the release entry will have
an idea of what it includes.
1. Provide a link to the new image release (e.g. `Image:
3. Provide a link to the new image release (e.g. `Image:
k8s.gcr.io/node-problem-detector/node-problem-detector:v0.8.6`)
## Post release steps