versionize-docs is dead

cherry-picks.md

@@ -42,24 +42,6 @@ label.
 There is an [issue](https://github.com/kubernetes/kubernetes/issues/23347) open
 tracking the tool to automate the batching procedure.
 
-#### Cherrypicking a doc change
-
-If you are cherrypicking a change which adds a doc, then you also need to run
-`build-tools/versionize-docs.sh` in the release branch to versionize that doc.
-Ideally, just running `hack/cherry_pick_pull.sh` should be enough, but we are
-not there yet: [#18861](https://github.com/kubernetes/kubernetes/issues/18861)
-
-To cherrypick PR 123456 to release-3.14, run the following commands after
-running `hack/cherry_pick_pull.sh` and before merging the PR:
-
-```
-$ git checkout -b automated-cherry-pick-of-#123456-upstream-release-3.14
-origin/automated-cherry-pick-of-#123456-upstream-release-3.14
-$ ./build-tools/versionize-docs.sh release-3.14
-$ git commit -a -m "Running versionize docs"
-$ git push origin automated-cherry-pick-of-#123456-upstream-release-3.14
-```
-
 ## Cherry Pick Review
 
 Cherry pick pull requests are reviewed differently than normal pull requests. In

how-to-doc.md

@@ -19,7 +19,6 @@ for Kubernetes.*
     - [Headings](#headings)
   - [What Are Mungers?](#what-are-mungers)
   - [Auto-added Mungers](#auto-added-mungers)
-    - [Is Versioned](#is-versioned)
     - [Generate Analytics](#generate-analytics)
 - [Generated documentation](#generated-documentation)
 
@@ -181,18 +180,6 @@ your md file that are auto-added. You don't have to add them manually. It's
 recommended to just read this section as a reference instead of messing up with
 the following mungers.
 
-
-### Is Versioned
-
-IS_VERSIONED munger inserts `IS_VERSIONED` tag in documents in each release,
-which stops UNVERSIONED_WARNING munger from inserting warning messages.
-
-```
-<!-- BEGIN MUNGE: IS_VERSIONED -->
-<!-- TAG IS_VERSIONED -->
-<!-- END MUNGE: IS_VERSIONED -->
-```
-
 ### Generate Analytics
 
 ANALYTICS munger inserts a Google Anaylytics link for this page.