DOC: update documentation release process [skip actions][skip azp][skip cirrus] (numpy#27247)

Author: mattip

doc/Makefile

@@ -118,12 +118,14 @@ endif
 	tar -C build/merge/$(TAG) -xf build/dist.tar.gz
 	git -C build/merge add $(TAG)
 	@# For now, the user must do this. If it is onerous, automate it and change
-	@# the instructions in doc/HOWTO_RELEASE.rst
+	@# the instructions in doc/RELEASE_WALKTHROUGH.rst
 	@echo " "
 	@echo New documentation archive added to ./build/merge.
 	@echo Now add/modify the appropriate section after
 	@echo "    <!-- insert here -->"
 	@echo in build/merge/index.html,
+	@echo change _static/versions.json,
+	@echo and run \"python3 update.py\"
 	@echo then \"git commit\", \"git push\"
 
 

doc/RELEASE_WALKTHROUGH.rst

@@ -272,18 +272,17 @@ If the release series is a new one, you will need to add a new section to the
     $ gvim index.html +/'insert here'
 
 Further, update the version-switcher json file to add the new release and
-update the version marked `(stable)`::
+update the version marked ``(stable)`` and ``preferred``::
 
     $ gvim _static/versions.json
 
-Otherwise, only the ``zip`` link should be updated with the new tag name. Since
-we are no longer generating ``pdf`` files, remove the line for the ``pdf``
-files if present::
+Then run ``update.py`` to update the version in ``_static``::
 
-    $ gvim index.html +/'tag v1.21'
+    $ python3 update.py
 
 You can "test run" the new documentation in a browser to make sure the links
-work::
+work, although the version dropdown will not change, it pulls its information
+from ``numpy.org``::
 
     $ firefox index.html  # or google-chrome, etc.
 
@@ -294,9 +293,8 @@ Update the stable link and update::
 
 Once everything seems satisfactory, update, commit and upload the changes::
 
-    $ python3 update.py
     $ git commit -a -m"Add documentation for v1.21.0"
-    $ git push
+    $ git push [email protected]:numpy/doc
     $ popd