Add release checklist

[atravitz]

Developers certificate of origin

• I certify that this contribution is covered by the MIT License here and the Developer Certificate of Origin at https://developercertificate.org/.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 92.84%. Comparing base (d24c6a7) to head (dfdb32d).
Report is 197 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1007      +/-   ##
==========================================
- Coverage   94.59%   92.84%   -1.76%     
==========================================
  Files         134      134              
  Lines        9940     9940              
==========================================
- Hits         9403     9229     -174     
- Misses        537      711     +174     

Flag	Coverage Δ
fast-tests	92.84% <ø> (?)
slow-tests	?

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[IAlibay]

What about adding the conda lock and single file installers to the release assets?

[mikemhenry]

That step happens after the conda-forge build is done/uploaded. Adding the assets is automated now 😎 but still requires a manual click to fire off (for now, we could automate it as well). So something like "After the conda-forge package is uploaded, start single file installer and docker image workflow (and verify it was successful)"

[atravitz]

I updated this to point to the wiki for all post-merge items. I think things are clearer this way. @mikemhenry ready for another look/approval. We will of course improve this during our next release process.

[IAlibay]

lgtm!