Create a new release for the announcement

[MathewBiddle]

Before we make the announcement we should push another release and update the DOI package. v2.0.0 or v1.1.0, I think the former as it's a significant change from v1.0.0.

@ocefpaf, you've cleaned a lot of this repo up and it would be nice to stamp this as a release.

See the current DOI package https://zenodo.org/record/5248490#.YUHxPZ1KiUk
Which uses this release https://github.com/ioos/ioos_code_lab/tree/v1.0.0

[MathewBiddle]

@ocefpaf, LMK when we are ready for this release and what the semantic versioning should be. I can make the release.

[MathewBiddle]

@ocefpaf, any thoughts on a new release?

[MathewBiddle]

started a draft https://github.com/ioos/ioos_code_lab/releases/tag/untagged-1a9f0abf3a295469a4b5

[MathewBiddle]

we will need to update https://github.com/ioos/ioos_code_lab/blob/main/CITATION.cff

[MathewBiddle]

might have a chicken before the egg problem with this

ioos_code_lab/CITATION.cff

Line 17 in cf243c9

version: v1.0.0

Update the citation file then push a new release?
Or, push a new release then update citation file?

[ocefpaf]

Update the citation file then push a new release?
Or, push a new release then update citation file?

No idea 😖

[MathewBiddle]

Let's go with update the citation file then push a new release. That way the canonical version number is incorporated into the release package.

[MathewBiddle]

I'd like to merge #11, then we can push the new release.

[MathewBiddle]

Shoot, we didn't do this...

[MathewBiddle]

Made a new release for v2.0.0
https://github.com/ioos/ioos_code_lab/releases/tag/v2.0.0