Update release process template to current process

galaxy_release_util/bootstrap_history.py

@@ -244,14 +244,6 @@
 
           make release-create-rc
 
-    - [ ] Create dev packages:
-
-          cd packages && DEV_RELEASE=1 ./build_packages.sh
-
-
-    - [ ] Review created packages (HISTORY.rst correct, setup.cfg correct, correct version in filename)
-    - [ ] Upload galaxy-util & galaxy-tool-util dev packages to pypi
-    - [ ] Open PR against planemo with a pin to the dev packages
     - [ ] Open PRs from your fork of branch ``version-${version}`` to upstream ``release_${version}`` and of ``version-${next_version}.dev`` to ``dev``.
     - [ ] Update ``MILESTONE_NUMBER`` in the [maintenance bot](https://github.com/galaxyproject/galaxy/blob/dev/.github/workflows/maintenance_bot.yaml) to `${next_version}` so it properly tags new PRs.
 
@@ -310,12 +302,8 @@
 
           cd packages && ./build_packages.sh
 
-
-    - [ ] Review created packages (HISTORY.rst correct, setup.cfg correct, correct version in filename)
-    - [ ] Upload built packages to pypi
-    - [ ] Add the branch `*/release_{version}` to Jenkins documentation build [configuration matrix](https://jenkins.galaxyproject.org/job/galaxy-sphinx-by-branch/configure).
-    - [ ] Trigger the [branch documentation build](https://jenkins.galaxyproject.org/job/galaxy-sphinx-by-branch/)
-    - [ ] Verify that everything is merged from ${version}->master, and then trigger the ['latest' documentation build](https://jenkins.galaxyproject.org/job/latest-Sphinx-Docs/)
+    - [ ] Create the first point release (v${version}.0) using the instructions at https://docs.galaxyproject.org/en/master/dev/create_release.html
+    - [ ] Open PR against planemo with a pin to the new packages
 
 - [ ] **Do Docker Release**