Merge pull request #1692 from yliaog/master

removed docs and scripts around submodules. submodules are no longer

Author: k8s-ci-robot

Diff for: devel/release.md

@@ -17,11 +17,7 @@ are a higher than expected number of issues there can be multiple releases
 
 ## Automated release
 
-### 1. (Optional) Update submodules
-
-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.
-
-### 2. Run the release script and send a PR
+### 1. Run the release script and send a PR
 Generate a Github personal access token following instruction
 [link](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)
 
@@ -49,11 +45,11 @@ $ KUBERNETES_BRANCH=release-1.${MINOR_VERSION} CLIENT_VERSION=${MINOR_VERSION}.$
 Checkout the generated local branch (named "automated-release-of-xxx") to
 continue with the remaining steps.
 
-### 3. README (not required for snapshots)
+### 2. README (not required for snapshots)
 
 Update the compatibility matrix and maintenance status in the README file.
 
-### 4. Submit pull request
+### 3. Submit pull request
 
 For snapshots, create a PR against the master repo.
 
@@ -62,17 +58,13 @@ For actual releases, create:
 - a second PR against the master branch to cherrypick the CHANGELOG and README
   changes.
 
-### 5. (Repo admin) Create release branch
+### 4. (Repo admin) Create release branch
 
 After merging a new snapshot, create a release branch from the master branch.
 
 ## (Deprecated) Manual release
 
-### 1. Update submodules
-
-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.
-
-### 2. Create or update release branch
+### 1. Create or update release branch
 
 The release branch name should have release-x.x format. All minor and pre-releases
 should be on the same branch. To update an existing branch with master (only for
@@ -89,7 +81,7 @@ git pull -X theirs upstream master
 You may need to fix some conflicts. For auto-generated files, you can commit
 either version. They will be updated to the current version in the next step.
 
-### 3. Update release tags
+### 2. Update release tags
 
 Release tags are in the "scripts/constants.py" file. These are the constants you
 may need to update:
@@ -126,7 +118,7 @@ apply the manual fixes.***
 git push upstream $RELEASE_BRANCH
 ```
 
-### 4. Hot issues
+### 3. Hot issues
 
 Use the `scripts/apply-hotfixes.sh` script to apply the fixes below in one step.
 **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.**
@@ -152,15 +144,15 @@ For more details, see [#974](https://github.com/kubernetes-client/python/issues/
 
 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.
 
-### 5. CHANGELOG
+### 4. CHANGELOG
 
 Make sure the change logs are up to date [here](https://github.com/kubernetes-client/python/blob/master/CHANGELOG.md).
 If they are not, follow commits added after the last release and update/commit
 the change logs to master.
 
 Then based on the release, follow one of next two steps.
 
-### 6. README
+### 5. README
 
 Update the compatibility matrix and maintenance status in the README file.