Skip to content

Commit 5c1cabf

Browse files
authored
Merge pull request #528 from stmcginnis/release-docs
Add notes on steps to perform when doing a release
2 parents e842171 + e7511e6 commit 5c1cabf

File tree

1 file changed

+47
-0
lines changed

1 file changed

+47
-0
lines changed

docs/release_process.md

Lines changed: 47 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,47 @@
1+
# Release Process
2+
3+
These are notes to help follow a consistent release process. See something
4+
important missing? Please submit a pull request to add anything else that would
5+
be useful!
6+
7+
## Preparing for a release
8+
9+
There are a few steps that should be taken prior to creating the actual release
10+
itself.
11+
12+
1. Collect changes since last release. This can be done by looking directly at
13+
merged commit messages (``git log [last_release_tag]...HEAD``), or by
14+
viewing the changes on GitHub ([example:
15+
https://github.com/kubernetes/node-problem-detector/compare/v0.8.6...master](https://github.com/kubernetes/node-problem-detector/compare/v0.8.6...master)).
16+
17+
1. Based on the changes to be included in the release, determine what the next
18+
release number should be. We strive to follow [SemVer](https://semver.org/)
19+
as much as possible.
20+
21+
1. Update [CHANGELOG](https://github.com/kubernetes/node-problem-detector/blob/master/CHANGELOG.md)
22+
with all significant changes.
23+
24+
## Create release
25+
26+
Once changes have been merged to the CHANGELOG, perform the actual release via
27+
GitHub. When creating the release, make sure to include the following in the
28+
body of the release:
29+
30+
1. For convenience, add a link to easily view the changes since the last
31+
release (e.g.
32+
[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)).
33+
34+
1. There is no need to duplicate everything from the CHANGELOG, but include the
35+
most significant things so someone just viewing the release entry will have
36+
an idea of what it includes.
37+
38+
1. Provide a link to the new image release (e.g. `Image:
39+
k8s.gcr.io/node-problem-detector/node-problem-detector:v0.8.6`)
40+
41+
## Post release steps
42+
43+
1. Update image version in
44+
[deployment/node-problem-detector.yaml](https://github.com/kubernetes/node-problem-detector/blob/422c088d623488be33aa697588655440c4e6a063/deployment/node-problem-detector.yaml#L32).
45+
46+
Update the image version in the deployment file so anyone deploying directly
47+
from the repo deployment file will get the newest image deployed.

0 commit comments

Comments
 (0)