Feature Request: create release tags for downstream packaging

[SuperSandro2000]

Is your feature request related to a problem? Please describe. I can't easily download a specific version from GitHub without searching through the commit history.

Describe the solution you'd like Tag release versions.

Describe alternatives you've considered Searching through the commit history which is not ideal.

Additional context

[DanielGoldfarb]

Sandro,

I understand that tags will make it easier to examine the code for a particular version, and it is definitely on my list of things to do, however it is not a high priority for me right now, compared to other changes we are trying to get done (and relative to how often we find the need to go back and examine the code for a particular version.

In the meantime I would suggest the following method for viewing the code corresponding to a particular version:

1. Examine release versions with release dates here: https://pypi.org/project/mplfinance/#history
2. Examine the PR history here: https://github.com/matplotlib/mplfinance/pulls?q=is%3Apr+is%3Aclosed
3. Find the latest PR that could have gone into the version you want. Let's say we are interested in version 0.12.7a5 which was released on 23-Jan-2021. From the PR history page we see the latest PR that could have gone into that version is PR #321
4. CLick on that PR and notice just above where it says "Pull request successfully merged" it will indicate the merge commit with a phrase something like: "... merged commit c036d31 into matplotlib:master on Jan 23" (If you want, you can also click on that commit number to verify that the version_info variable changed to the version you want.)
5. Create a new branch with that version. For example:

   ~/code/mplfinance$ git checkout -b v0.12.7a5 c036d31
   
   Switched to a new branch 'v0.12.7a5'
   

HTH. All the best. --Daniel