GitHub releases for Foundations

[brian-rose]

Following up on #239, I think we should start minting "releases" of the Foundations source on GitHub. We can use calendar versioning, e.g. v2022.11.23.

I think a sensible policy would be to mint a new release whenever there's a non-trivial change in content, e.g. a new chapter added, revisions to code in a notebook, etc. Or, a change in infrastructure that affects the viewable content (such as updated JupyterBook theme).

One motivation for this is mentioned in the discussion linked above -- it lets people set notifications for themselves about new releases. I think it also signals vitality of the project.

I suggest we issue the first "release" in advance of AGU once we've gotten through the updates discussed at the last EWG meeting.

[brian-rose]

This is related to our plans to use Zenodo to issue DOIs for Foundations and Cookbooks. We should proceed with Foundations as a test case for all Cookbooks.

[jukent]

I made a release just to test it, and gave Zenodo permissions to this repository but it isn't all in place yet - just starting the exploration process.

https://zenodo.org/account/settings/github/repository/ProjectPythia/pythia-foundations#

[jukent]

Remaining work: what means a new release?