Add a RELEASE.md file to document and track the release process of the heartwood binaries.

Run shellcheck on the tagging script, rewrite it and fix some minor errors.

Fixes.

Rebase

Fill out the rest of document

Rebased

In the last line of the RELEASE.md, the last link is broken:

[...] and [Bluesky][bsk].

But the link name is [bsky]!

There is nothing said about the release process for patch-releases, if I didn’t miss anything. Do we need something for how patch-release branches are done and how patches are backported if need be?

Adjust for the new release tags

See the REVIEW commits

This should probably include a few words on how to make the Debian releases too. Unfortunately, I don’t feel I’m knowledgable enough to contribute that text

Changes:

• Rebase
• Fixup to copy
• Accept richard’s feedback

RELEASE: include patch releases

Document the workflow of patch releases.

Rebase