CMOR 3.7

[mauzey1]

• Change configure.ac to 3.7.0 and rerun autoconf.
• Verify that optimization is disabled from setup.py.in.
• Review all issue lists and close all redundant issues (move unresolved issues to next milestone)
• Validate version info is correctly written (CMOR version should be 3.7.0)
• Validate data_specs_version written (01.00.33)
• Increment CMOR 3.6.1 in INSTALL file to CMOR 3.7.0
• Run all tests
• Update master branch
• Get the latest CMIP6_CV.json in cmip6-cmor-tables using the cronjob script.
• Set 3.7.0 tag point in PCMDI/cmor repo
• Create conda-forge version 3.7.0 in cmor-feedstock
• Test cmor 3.7.0 from conda-forge conda create -n cmor3.7.0 -c conda-forge cmor
• [ ] Update conda env export > cmor_3.7.0.yaml file
• Prepare and publish release notes to CMOR website
• Create new Release 3.7.0 in PCMDI/cmor
• Update website so correct tag points (3.7.0) are noted for build notes
• Create PDF from website. (use jekylll build and Prince). post new tag to cmor3_documentation.
• Obtain Zenodo DOI (not needed linked to latest release automatically)
• Update README.md with updated Stable version info (should be 3.7.0) and updated Zenodo DOI info
• Email cmor@llnl.gov, including the text: Please pass on this email to anyone you know who plans to prepare CMIP6 model output for the archive.

[durack1]

@mauzey1 it'd be great if we can add resolving #628 to this tasklist - this will likely require some iteration/testing, which I am happy to do

[mauzey1]

@durack1 That is already on the to-do list of the release project. https://github.com/PCMDI/cmor/projects/8

[durack1]

@mauzey1 perfect, thanks!

I wonder if there are any other little items in the current issue list that we could also allocate for the 3.7.0 release - @taylor13 is on vacation at the moment, but it might be worthwhile that we cover this before the release

[durack1]

@mauzey1 we'll need to tweak the author list for the Zenodo entry, it seems that things need a bit of a tweak - https://zenodo.org/record/4328851

Some syntax controls can be found in the example json - see https://github.com/PCMDI/pcmdi_metrics/blob/main/.zenodo.json, which displays as https://zenodo.org/record/5784459 (PC<DI Metrics v2.2.1)

[durack1]

Also add noted tweaks to the Fortran wrapper, documented in PCMDI/cmip6-cmor-tables#377

[mauzey1]

@durack1 For the Zenodo author list, who would we list? The current list seems to be everyone who contributed code to the project through GitHub. Should the authors just be the main current developers?

[durack1]

@mauzey1 good question. It seems the 3.6.1 lists all contributors, plus some. It would be nice to clean the names up so we have complete names rather than github handles.

I think we go with the core team, plus contributors, so:

Chris Mauzey, Karl E. Taylor, Paul J. Durack, Charles Doutriaux, Denis Nadeau, Emma Hogan, Jamie Kettleborough, Tobias Weigel, kjoti, jmgonza, Zeb Nicholls, Edward Betts, Jon Seddon, Fabian Wachsmann (not sure we can expand from github names)

@taylor13 any suggestions?

[mauzey1]

@durack1 We should also add Piotr Florek (@piotr-florek-mohc) to the list.

[durack1]

@mauzey1 absolutely, and anyone else I erroneously omitted

[durack1]

@mauzey1 please let me know if I have showstopper PRs or issues that are getting in the way of this CMOR3.7.0 release

[mauzey1]

@durack1 I'm currently resolving issues related to the CircleCI nightly build and conda-forge feedstock. I think I have the nightly build issue resolved so I will merge those into the CMOR 3.7.0 branch soon.

[durack1]

@mauzey1 excellent news, looking forward to seeing this live!

[mauzey1]

@durack1 Should I send emails to cmor@llnl.gov and pcmdi-cmip@llnl.gov about this release?

[durack1]

@mauzey1 yes please, just the cmor address, as the pcmdi-cmip is just 4 people (inside LLNL, plus @matthew-mizielinski)

[mauzey1]

Okay, I will just send a message through the CMOR mailing list. I think that should be the only mailing list that we should use so we don't come off like spam on the other ones.