Provide changelog and tagged releases

[stefan6419846]

As initially pointed out in orcasgit/django-fernet-fields#28 (comment), while this project has PyPI releases, there seem to be no tags/releases available on GitHub, which would map to the PyPI releases. Additionally, no changelog is provided.

This makes it very hard to check what to expect from an update beforehand, while even tracking down a version where a possibly breaking/problematic change has been introduced is unnecessarily complex.

For this reason, I ask you to at least tag your releases and provide a meaningful changelog for each version.

[suricactus]

Just came to the repo to request this. I am available if the maintainers need any help that I can provide in resolving this issue.

[Christophe31]

I use to put changelog links in my dependencies list as comment to read before bump. I won't be able for this one as long as it does not exist.

[frgmt]

Does this look alright for the changelog?
#43

[Christophe31]

Thank you for your quick contribution.

It's perfect.

I may have put a "0.4.1 [unreleased]" section to avoid a bump while there is no code change yet and encouraging filling it in each merge request.

Even though it's not the question, I would not make a release for doc and tooling changes if there is no dependencies or code changes..