Tag releases in Git(Hub)

[kevin-brown]

There have been quite a few releases of sendgrid-django, as indicated by PyPI, but these releases don't appear to be tagged on GitHub. For those of us who don't upgrade as fast as everyone else, this makes it difficult to hunt down the source for our version of the package when we want to view it on GitHub.

Would it be possible for a tag to be created or a release to be created for future versions of sendgrid-django, to make it easier to track down versions of the package and compare them?

[andriisoldatenko]

@kevin-brown It's good idea and practice.
I think we should add something to project like https://github.com/peritus/bumpversion
I can create PR :)
What do you think @elbuo8

[elbuo8]

@andriisoldatenko that looks interesting. Go for it 👍

[richardxia]

👍
In addition, it'd be good to clearly explain backwards incompatible changes and the upgrade steps. I hadn't upgraded in about 9 months and had to carefully read the commit history in order to figure out that the SENDGRID_USER/SENDGRID_PASSWORD settings were removed in favor of SENDGRID_API_KEY.

[dwasyl]

+1 A CHANGELOG document would also be extremely useful. I'm at version 1.4.0 and trying to figure out if I can upgrade to 4.0.4 is quite a challenge.

But, even just tagging the releases would be extremely helpful!