Create (and document) a release tag process

[slifty]

We just shipped some code to production; we should use tags to keep track of when a release.

This should come with documentation, as well as documentation for patches. We should retroactively invoke the process for the release we just made.

Eventually this should be used for continuous deployment to staging, which is is a separate issue.

[reefdog]

Very much yes. It'll be so nice/valuable to be able to know exactly what code shipped to production and when.

My take on version numbering for this app specifically is it is essentially meaningless, so my preference would be for doing whatever is the least amount of work and won't require us to spend time thinking/discussing each release, unless/until an argument justifies that. So, literally tagging with the most recent commit hash (v33e70ce) would be perfectly acceptable to me.

But if you feel otherwise and think a case can be made for semver'ing on a time budget, go for it!

[reefdog]

(If we go that route but suspect we might later want true version numbers, we could use a different prefix than v, perhaps r. E.g., r33e70ce.)