no github release for 1.0

[robertlemmen]

I have worked out why I sometimes end up with ancient versions of json::tiny: there is no github release (https://github.com/moritz/json/releases) for the 1.0 that is on CPAN. I guess it only needs a tag...

[jnthn]

If it's being distributed by CPAN, why would what's on GitHub matter?

[robertlemmen]

that is an ok position, but then it would be better to not have any releases on the github page. they otherwise suggest that this is a (alternative) place to get releases. also independently from the question of where you get your releases, having a tag for a release is certainly a nice thing.

but none of this is a problem of course, I just noticed it and wanted to point it out. I would want to know if I had made a release on CPAN without a matching tag in my repo...

[AntonOks]

if you think outside your "RAKU" box, just "plain developer thinking"... showing a "important spacial commit", that's what GIT TAGS are for, right!!?!

I don't really understand the "RAKU developers", which DO maintain a local "MATA6.json" file (as it's needed for ZEF [and maybe other RAKU related tools?], as far as I understand) and by this show they have changes and do "release" a kind of new version, but DO NOT also use GIT properly as well.

PLEASE add also GIT TAGS if you change your "RAKU module" (so at the same time as you do change the META6.json!). This is especially required for the "RAKUDO STAR" bundle, which installs modules... and maintaining the list of modules in a manual way is gonna go away... but to have a "recent" modules.txt generated GIT TAGs are required.

THANKS!!!