🌟 Release Checklist for TIDES v1.0

[e-lo]

This issue tracks outstanding items that must be completed before declaring a full release.

Remaining Issues from Milestone

Requirements from Versioning Policy

• Each release MUST contain one or more changes to normative content which have been approved through the change-making process.
• Each release MUST be reviewed and approved in GitHub by 2+ members of the Board – or their designees – for accuracy and consistency with the changes’ intent.
• Each release MUST be tagged with its version number.
• Each release MUST have documentation available.
• Each release MUST have an entry in CHANGELOG.md.
• Each release MUST be specified as a release on Github.
• Each release MUST be noticed to any TIDES mailing lists or discussion groups.
• Each release SHOULD have sample datasets (real or exemplary) which cover the normative changes in the release.