Consider requiring conventional commit messages

Currently releases take a lot of time, as I need to go through the git commits and figure out new features vs bugfixes, reformat messages, etc. Requiring things like fix/feature/etc tags, and perhaps some consistency of change description, would make the release process simpler.

People who have experience with such schemes on other projects - any thoughts?

The issue names no files, tests, or entry points; begin by reviewing the existing release process and commit history. Done would require an agreed commit convention and a documented or enforced change that makes release classification consistent.

Written by the indexing model from the issue text.