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: devel/release.md
+46-9Lines changed: 46 additions & 9 deletions
Original file line number
Diff line number
Diff line change
@@ -15,11 +15,50 @@ report issues. Typically, there is a single alpha or beta release, but if there
15
15
are a higher than expected number of issues there can be multiple releases
16
16
(e.g, a2 or b2).
17
17
18
-
## 1. Update submodules
18
+
## Automated release
19
+
20
+
### 1. (Optional) Update submodules
21
+
22
+
Update submodules by referring to this [link](https://github.com/kubernetes-client/python/blob/master/devel/submodules.md#update-submodule). Commit the changes and open a pull request.
23
+
24
+
### 2. Run the release script and send a PR
25
+
26
+
```
27
+
export MINOR_VERSION=x
28
+
export PATCH_VERSION=y # The latest patch version for the minor version. Not required for snapshot.
Update the compatibility matrix and maintenance status in the README file.
49
+
50
+
### Submit pull request
51
+
52
+
Typically after the you've completed steps 2-6 above you can push your changes
53
+
open a pull request against `kubernetes-client:release-x.y`
54
+
55
+
## (Deprecated) Manual release
56
+
57
+
### 1. Update submodules
19
58
20
59
Update submodules by referring to this [link](https://github.com/kubernetes-client/python/blob/master/devel/submodules.md#update-submodule). Commit the changes and open a pull request.
21
60
22
-
## 2. Create or update release branch
61
+
###2. Create or update release branch
23
62
24
63
The release branch name should have release-x.x format. All minor and pre-releases
25
64
should be on the same branch. To update an existing branch with master (only for
You may need to fix some conflicts. For auto-generated files, you can commit
37
76
either version. They will be updated to the current version in the next step.
38
77
39
-
## 3. Update release tags
78
+
###3. Update release tags
40
79
41
80
Release tags are in the "scripts/constants.py" file. These are the constants you
42
81
may need to update:
@@ -73,7 +112,7 @@ apply the manual fixes.***
73
112
git push upstream $RELEASE_BRANCH
74
113
```
75
114
76
-
## 4. Hot issues
115
+
###4. Hot issues
77
116
78
117
Use the `scripts/apply-hotfixes.sh` script to apply the fixes below in one step.
79
118
**As mentioned above, the script should be run after finishing the section "Update release tags". Also, ensure a clean working directory before applying the script.**
@@ -99,19 +138,19 @@ For more details, see [#974](https://github.com/kubernetes-client/python/issues/
99
138
100
139
5. Add tests for the default `Configuration` behavior (ref: https://github.com/kubernetes-client/python/pull/1303 and https://github.com/kubernetes-client/python/pull/1285). The commit [1ffa61d0650e4c93e0d7f0becd2c54797eafd407](https://github.com/kubernetes-client/python/pull/1285/commits/1ffa61d0650e4c93e0d7f0becd2c54797eafd407) should be cherry-picked.
101
140
102
-
## 5. CHANGELOG
141
+
###5. CHANGELOG
103
142
104
143
Make sure the change logs are up to date [here](https://github.com/kubernetes-client/python/blob/master/CHANGELOG.md).
105
144
If they are not, follow commits added after the last release and update/commit
106
145
the change logs to master.
107
146
108
147
Then based on the release, follow one of next two steps.
109
148
110
-
## 6. README
149
+
###6. README
111
150
112
151
Update the compatibility matrix and maintenance status in the README file.
113
152
114
-
## Submit pull request
153
+
###Submit pull request
115
154
116
155
Typically after the you've completed steps 2-6 above you can push your changes
117
156
open a pull request against `kubernetes-client:release-x.y`
@@ -220,6 +259,4 @@ deactivate
220
259
rm -rf .release
221
260
```
222
261
223
-
TODO: Convert steps in this document to an (semi-) automated script.
0 commit comments