Changelog for 2.1.x

[vbgamer45]

Noticed on the download section there is a changelog for 2.0.19 but not for SMF 2.1.4.

[Sesquipedalian]

We stopped publishing a standalone changelog when we moved to a public GitHub repository.

[vbgamer45]

Ah ok just thought it looked odd.

[Illori]

We stopped publishing a standalone changelog when we moved to a public GitHub repository.

maybe worth putting a link to github instead?

[Sesquipedalian]

That's probably a good idea. That change would need to be made by @SleePy.

[SleePy]

How do we want to link?  Just to the straight Github, or do we need to link to that branch's changelog?

[live627]

Perhaps link to the releases page where change notes should be published.

[Sesquipedalian]

The best option would be to use this URL template for each release:

https://github.com/SimpleMachines/SMF/compare/v2.1.3...v2.1.4

[SleePy]

Ok, I think I can do that.  As long as we follow the naming of our versions on SM the same as they are tagged on GitHub, I can auto-generate the URL.

[Sesquipedalian]

The last part of the URL will always use two Git tags (e.g "v2.1.3" and "v2.1.4" above). We always use semantic versioning for the tags, so a simple script that assumes we will continue to do that should work fine. But you could also pull the tags directly from the Git repo if you want to do that way.

[SleePy]

Well, we didn't always follow the semantic versioning, so I just added a column to track the tag on the version table.  The downloads site is updated.  When we publish a new version, a "blank" file forthe  changelog is added.  It was easier to do that then adding a virtual entry for the change log.