modules.perl6.org should link each module name to the latest release url about ecosystem

[moritz]

What's the user experience like if we do that? Will the link be a tarball? If yes, then I don't think that's a good idea.

Do you have an example of how it would look like?

[tbrowder]

On Monday, October 10, 2016, Moritz Lenz [email protected] wrote:

What's the user experience like if we do that? Will the link be a tarball?
If yes, then I don't think that's a good idea.

Per ugexe's commnts, and my current understanding, the url would be to the
release commit tree on the master branch (or any other branch if
appropriate) so the module link on the modules.perl6.org would take the
clicker to that commit tree so he could see the actual released code.

Do you have an example of how it would look like?

I was waiting for confirmation from ugexe that it will work (he may have to
do a little code mod on the ecosystem). But I will update my module's
current master branch META6.json to show the link.
...

I have updated my module's META6.json in https://github.com/tbrowder/Net-IP-Lite-Perl6/ to point to the latest release code tree.

[JJ]

Could this be related to #433 ?

[tbrowder]

Yes, let's close this.