Right now, the versioning system is embedded in the HTML form, does not follow widely adopted convention, and is out-of-sync from GH Releases.
In the future I would like these changes:
Contributors (myself especially) follow the semantic versioning convention, numbers only, denoting MAJOR.MINOR.PATCH levels to denote breaking changes, feature enhancements, and bug fixes (accordingly).
Ensure the declared version is updated in the HTML file so each data-entry operator knows they have the correct (latest) version.
Ensure the declared version is updated in the template TXT file so the recipient sees within the message that the correct (latest) version was used to construct the message.
Stretch Goal: Find a way to manage versioning without hard-coding (perhaps with GH Actions).
nojronatron
commented
1 year ago
Right now, the versioning system is embedded in the HTML form, does not follow widely adopted convention, and is out-of-sync from GH Releases.
In the future I would like these changes: