Release v3.30.23 checklist

[e-perl-NOAA]

Release checklist

Initial checklist

• SS3 testing and debugging completed (RM/IT/EP)
• Check artifact from the call-build-ss3-warnings GitHub action for useful warnings (RM/IT)
• r4ss updated (IT/EP)

Checklist for before release

• The following steps should be encompassed in the new manual release workflow and bug fix release workflow and can be deleted at a future time once the new manual release workflows have been used for a couple releases (EP).
  • Manual updated and tagged in repo (EP) - address at least issues with the [v3.30.23 release label](add correct link to GitHub issues using filter: is:issue is:open label:"3.30.23 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.23 version; update links to link to v3.30.23 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 updated with any issues labelled "change log" (RM)
• Code committed and tagged in repo as v3.30.23, which will trigger a GHA to build the release executables (EP) (Instructions on how to push a a local tag to a remote)
• Exe and .tpl archived on Google drive (EP)
• All exes added to GitHub releases as v3.30.23 (EP) (get exes in the artifacts of the GHA that built the release exes)
• Send out release announcement message to the SS3 forum (RM)
• Add to release discussion on GitHub repository (EP)

Checklist for after release

• Update user-example models using this github action and tag with new release number after updating (EP)
• Update test models using this github action and tag with new release number after updating (EP)
• Update executables in the SAC tool (also suggest updating the input files to the .ss_new files (EP/JC)
• Removed "resolved" tag and close all issues worked in the milestone for this release (RM)
• Move unworked issues for the release milestone to the next milestone (RM)