Please create git tags for releases

[mgorny]

We packagers find git tags very convenient for fetching release versions from GitHub. Could you please create and push tags corresponding to releases (or at least the most recent release)?

[mcepl]

And/or please also package tests to the distribution tarball. Many Linux (not only) distros try to run a test suite of packages to make sure that at least something on the package is working and they are not delivering to their users just useless turd.

[kloczek]

+1

[kloczek]

gentle ping 😃

[hswong3i]

I am facing the same issue, e.g. I could only link these together:

• 1.1.1
  • https://build.opensuse.org/package/show/home:alvistack/tabatkins-railroad-diagrams-1.1.1
  • d039911
• 2.0.3
  • https://build.opensuse.org/package/show/home:alvistack/tabatkins-railroad-diagrams-2.0.3
  • b4e5333

Another good idea is not only about GIT tag, but also create a GitHub Release accordingly. For my daily use case I will enable notification for each repo with "Release", therefore I could create a new deb/rpm package for it within the next day, and provide bugfix PR to upstream ASAP ;-)

[UPDATE] Well... bugfix PR to upstream comes for fixing 2.0.3 available for Python < 3.7... See #96

[mgorny]

Another good idea is not only about GIT tag, but also create a GitHub Release accordingly. For my daily use case I will enable notification for each repo with "Release", therefore I could create a new deb/rpm package for it within the next day, and provide bugfix PR to upstream ASAP ;-)

I suggest putting pypi release feeds in your feed reader, they're a great way to get updates on Python packages. Especially when upstreams forget to push tags.

[hswong3i]

I suggest putting pypi release feeds in your feed reader, they're a great way to get updates on Python packages. Especially when upstreams forget to push tags.

As a packager I have a more simple stupid solution:

1. Create a podman instance with Ubuntu 18.04 for Python 3.6 and Ubuntu 20.04 for Python 3.8
2. Install corresponding packages from my OBS repo
3. Running pip list --outdated for checking

This could also check if my packaging script really works, especially about the version number generated for .egg-info.

Sometime I also run the target apps, eg ansible --version or molecule --version manually for checking if any runtime issue happened.

[mgorny]

Thanks, I didn't know about that one. As a bonus, it just made me discover some packages that put incorrect versions into dist-info.

[kloczek]

Gentle ping .. 😋
Can we have maintainer some comment? 🤔 Please ..

[lemenkov]

Hello! Thank you for this library I am using indirectly.
I would really love to see git tags as well :)