search

tabatkins / railroad-diagrams

:steam_locomotive: A small JS+SVG library for drawing railroad syntax diagrams, like on JSON.org. Now with a Python port!
MIT License
1.66k stars 153 forks source link

Please create git tags for releases #91

Open mgorny opened 3 years ago

mgorny commented 3 years ago

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 commented 3 years ago

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 commented 2 years ago

+1

kloczek commented 2 years ago

gentle ping 😃

hswong3i commented 2 years ago

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

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 ;-)

image

[UPDATE] Well... bugfix PR to upstream comes for fixing 2.0.3 available for Python < 3.7... See https://github.com/tabatkins/railroad-diagrams/pull/96

mgorny commented 2 years ago

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 commented 2 years ago

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 commented 2 years ago

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 commented 1 year ago

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

lemenkov commented 1 year ago

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