Update ss3-release-template.md (#650)

- Remove previous manual workflow to release ss3-doc (this is automated now and has been tested in 2 releases). 
- Rearrange the checklist to make more sense.

.github/ISSUE_TEMPLATE/ss3-release-template.md

@@ -20,6 +20,7 @@ assignees:
 - [ ] SS3 testing and debugging completed (RM/IT)
 - [ ] Check artifact from the `call-build-ss3-warnings` GitHub action for useful warnings (RM/IT/EP)
 - [ ] r4ss updated (IT/EP)
+- [ ] [Change log project board](https://github.com/orgs/nmfs-ost/projects/11) updated with any issues labelled "change log" and check for any issues that should be labelled "change log" (RM)
 
 <!---## Checklist for before pre-release (if pre-release is being done)
 - [ ] Put together pre-release announcement (RM)
@@ -28,15 +29,11 @@ assignees:
 - [ ] Announce prerelease (RM)-->
 
 ## Checklist for before release
-- [ ] The following steps should be encompassed in the new manual [release workflow](https://github.com/nmfs-ost/ss3-doc/actions/workflows/release.yml) and [bug fix release workflow](https://github.com/nmfs-ost/ss3-doc/actions/workflows/release_bug_fix.yml) and can be deleted at a future time once the new manual release workflows have been used for a couple releases (EP). **Note that the branch protection rules must be briefly turned off to allow this workflow to run**
-  - [ ] Manual updated and tagged in repo (EP) - address at least issues with the [`v3.30.xx` release label](add correct link to GitHub issues using filter: is:issue is:open label:"3.30.xx release" when available)
-  - [ ] Manual added to a GitHub release, include attaching a pdf version (EP)
-  - [ ] Manual release version on website updated once pdf and html built (EP) (update https://github.com/nmfs-ost/ss3-doc/blob/main/docs/SS330_User_Manual_release.html to the `v3.30.xx` version; update links to link to `v3.30.xx` in https://github.com/nmfs-ost/ss3-doc/blob/main/docs/index.md#links-to-documentation)
 - [ ] Make changes to SS3 if any bugs caught in prerelease (RM)
-- [ ] [Change log project board](https://github.com/orgs/nmfs-ost/projects/11) updated with any issues labelled "change log" (RM)
 - [ ] Code committed and tagged in repo as `v3.30.xx`, which will trigger a GHA to build the release executables (EP) (Instructions on [how to push a a local tag to a remote](https://github.com/nmfs-ost/ss3-source-code/wiki/Stock-Synthesis:-practices-for-maintainers#how-to-push-a-local-tag-up-to-github))
-- [ ] Exe and .tpl archived on [Google drive](https://drive.google.com/drive/folders/1Gh_dXi8v3rqawpwn2N6yaaEXZPq6G2io) (EP)
 - [ ] All exes added to GitHub releases as `v3.30.xx` (EP) (get exes in the artifacts of the GHA that built the release exes)
+- [ ] Run [release workflow](https://github.com/nmfs-ost/ss3-doc/actions/workflows/release.yml) (or [bug fix release workflow](https://github.com/nmfs-ost/ss3-doc/actions/workflows/release_bug_fix.yml) if the release is a bug fix). **Note that the branch protection rules must be briefly turned off to allow this workflow to run.** (EP)
+- [ ] Exe and .tpl archived on [Google drive](https://drive.google.com/drive/folders/1Gh_dXi8v3rqawpwn2N6yaaEXZPq6G2io) (EP)
 - [ ] Send out release announcement message to the [SS3 forum](https://groups.google.com/g/ss3-forum) (RM)
 - [ ] Add to release discussion on GitHub repository (EP)