You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: RELEASE.md
+10-4
Original file line number
Diff line number
Diff line change
@@ -2,19 +2,25 @@
2
2
3
3
The Kubebuilder Project is released on an as-needed basis. The process is as follows:
4
4
5
-
1. An issue is proposing a new release with a changelog since the last release
5
+
1. An issue is proposing a new release with a changelog since the last release. You will need to use the [kubebuilder-release-tools][kubebuilder-release-tools] to generate the notes. See [here][release-notes-generation]
6
6
1. All [OWNERS](OWNERS) must LGTM this release
7
-
1. An OWNER runs `git tag -s $VERSION` and inserts the changelog and pushes the tag with `git push $VERSION`
8
-
1. A PR needs to be created to merge `master` branch into `book-v2` to pick up the new docs.
7
+
1. An OWNER runs `git tag -s $VERSION` and pushes the tag with `git push $VERSION`. Note that after the OWNER push the tag the CI will automatically add the release notes and the assets.
8
+
1. A PR needs to be created to merge `release-X` branch into `book-vX` to pick up the new docs.
9
9
1. The release issue is closed
10
10
1. An announcement email is sent to `[email protected]` with the subject `[ANNOUNCE] kubebuilder $VERSION is released`
11
11
12
-
Note: This process does not apply to EAP or alpha (pre-)releases which may be cut at any time for development
12
+
**Notes:** This process does not apply to EAP or alpha (pre-)releases which may be cut at any time for development
13
13
and testing.
14
14
15
+
For further information about versioning and update the Kubebuilder binaries check the [versioning][release-process] doc.
16
+
15
17
## HEAD releases
16
18
17
19
The binaries releases for HEAD are available here:
0 commit comments