Pre-release Checklist from Versioning Policy

• Each pre-release MUST contain one or more changes to normative content which have been approved through the change-making process.
• Each pre-release MUST be reviewed and approved in GitHub by 1+ members of the board – or their designees – for accuracy and consistency with the changes’ intent.
• Pre-releases MUST be tagged with an appropriate pre-release version number
• Each pre-release MUST have documentation available.
• Each pre-release MUST have an entry in CHANGELOG.md.
• Each pre-release MAY be specified as a pre-release on Github.

Additional items for Beta release

• All (planned) normative content changes completed