3.30.20 release checklist

[k-doering-NOAA]

It's not yet time for the 3.30.20 release (we are waiting on a final version of ADMB 13), but feel free to add notes about the release here

Checklist for before prerelease

• Update GHA to use ADMB 13 (IT)
• SS testing and debugging completed (IT)
• r4ss updated (IT)
• Put together pre-release announcement (RM)
• code committed and tagged in repo as v3.30.20-prerel, which will trigger a gha to build the prerelease executables (KJ)
• All exes added to github releases as v3.30.20-prerel (KJ) (use exe artifacts from the gha in step above)
• Announce prerelease (RM)

Checklist for before release

• Manual updated and tagged in repo (CW) - address at least issues with the 3.30.20 release label
• Manual added to a github release, include attaching a pdf version (KJ and CW)
• Manual release version on website updated once pdf and html built (KJ) (update https://github.com/nmfs-stock-synthesis/doc/blob/main/docs/SS330_User_Manual_release.html to the 3.30.20 version; update links to link to 3.30.20 in https://github.com/nmfs-stock-synthesis/doc/blob/main/docs/index.md#links-to-documentation)
• SSI updated and github release created (NS)
• Make changes to SS3 if any bugs caught in prerelease (RM)
• Check that ADMB version listed in files is correct (RM)
• Change log updated in Stock Synthesis repo (RM)
• Code committed and tagged in repo as v3.30.20, which will trigger a gha to build the release executables (KJ) (Instructions on how to push a a local tag to a remote)
• Exe and .tpl archived on Google drive (KJ)
• All exes added to github releases as v3.30.20 (KJ) (get exes in the artifacts of the gha that built the release exes)
• Send out release announcement msg (RM)

Checklist for after release

• examples updated in user-examples repo using this script (KJ)
• Update test-models reference files to the release version using this update script (EG). also tag after updating with release number.
• 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)

[k-doering-NOAA]

@kellijohnson-NOAA has kindly agreed to coordinate this release, so she will be making sure the checklist gets completed when the time comes for the release.

[k-doering-NOAA]

Note I reassigned tasks that I usually do to coordinate a release (by changing initials in the checklist), so please take a look and let me know if you have any concerns about any new tasks! I will be available to answer questions if they arise.

[Rick-Methot-NOAA]

The change log was still a blank slate for 3.30.20. So rather than create al those entries, I am trying to just improve the labelling and linking for all the PRs and Issues in Milestone 3.30.20. Is a milestone view publicly accessible?

We can improve this approach by:

• assuring that every PR is linked to its originating issue
• adding Milestone designation to each PR
• adding at least one Label to each PR (like selectivity)

[kellijohnson-NOAA]

If you navigate to issues you can enter

milestone:3.30.20 

in the search bar and it will search for issues and pull requests with that milestone.

[iantaylor-NOAA]

This is an area where Kathryn was the key to making the changelog happen.

Kelli's search could be linked in a release message but the list is pretty messy: https://github.com/nmfs-stock-synthesis/stock-synthesis/issues?q=milestone%3A3.30.20+

I was just looking at github projects and see that they are private by default. For instance, this milestone tracker is not visible when I'm not logged into github https://github.com/orgs/nmfs-stock-synthesis/projects/2/views/1, but it could easily be made public. It's a cleaner list for folks to look at, but still not great.

If you want a change log like what we've done in the past, I can budget some time tomorrow or next week to try to populate one.

[Rick-Methot-NOAA]

Thanks for feedback. I know how to do it myself, what I am looking for is something that any user could easily do. Given that none of the issues and PR were documented in the change log yet, I think it better to find a way to do it with github tools. I agree that a project table will be cleaner looking that the milestone list and that probably is the way to go. But it requires that all items get labelled so they can be automatically displayed in the project table.