changelog, tags, and versioning

[ehough]

I'm curious if you've given any thought to any of the following versioning tools:

• keeping a separate changelog, either in a CHANGELOG file or via GitHub's Releases feature (see next bullet point)

• Tagging releases

• Semantic versioning, though it looks like you may already be adhering to this?

As a user, I expect and find it convenient to see a separate changelog, and I found it a little unusual to see one embedded within the script. Was there any reason you went that route?

[mviereck]

Thanks for this inspiration!
Thinking about this, the changelog and versioning can and should be improved. I am not sure which way to choose, I will look closer at the possibilities.

Semantic versioning, though it looks like you may already be adhering to this?

Mainly I am already doing this, but reading the rules again shows me that I should follow this more precisely in future.

As a user, I expect and find it convenient to see a separate changelog, and I found it a little unusual to see one embedded within the script. Was there any reason you went that route?

Just an old habit, no special reason. Mostly I am scripting only for myself, and I like to keep it simple. Having the changelog in the script means, I always know where it is and can see the state of the script.

[mviereck]

I've outsourced the changelog to a file CHANGELOG.md. Looks better now, indeed.

[ehough]

Looks great. And much easier to follow. Nice work!