add maintainer documentation on release process #57
Description
Release process for maintainers of the scale-av user manual, including the use of semver for versioning, has been internally discussed but has yet to be formally documented. Documentation should include the following:
- what constitutes a major/breaking release (e.g., removing content)
- what constitutes a minor/feature release (e.g., adding content)
- what constitutes a patch release (e.g., fixing a typo)
- process for tagging/categorizing issues/PR's according to level of change (major/minor/patch) that will influence upcoming releasing