In #307 the project switched to semantic versioning and started to cut regular release tags accordingly.

Discussion in #346 prompted the request that ZLint start providing "release candidate" releases before finalizing final releases. The general idea being to provide a more formalized pre-release that CAs and other consumers can use to test a to-be-released tag before it is finalized.

If this practice makes sense to everyone we should describe it in the README/CONTRIBUTING docs. I think it also makes sense to consider adding a script or tool to the repo that would make cutting release candidate and final releases repeatable and error free. Using something like https://goreleaser.com/ (my personal pref) would also make it easy to provide binary artifacts with releases as opposed to the current src-only method.