You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currrently there is no link from a charm page (such as https://jujucharms.com/landscape-client/ ) to where the upstream code lives, so it's very hard for someone to know where they should submit charm changes.
The text was updated successfully, but these errors were encountered:
Note that there's http caching in place so once the urls are set it'll take 10-15min for the changes to show on the charm webpage. It will work immediately from the cli:
charm show cs:landscape-client bugs-url
charm show cs:landscape-client homepage
Also, a bugs URL or homepage is informative, but not definitive. There is currently no way to say reliably which upstream repository, commit or tag was used when publishing a charm.
It's often possible to track back via the project homepage or bug submission link, where hopefully the charm author is diligent about tagging their releases in relation to uploads to the charm store - this is not always the case, and open to interpretation as well, as there is no definitive linkage between the source of a charm, and the uploaded charm.
Currrently there is no link from a charm page (such as https://jujucharms.com/landscape-client/ ) to where the upstream code lives, so it's very hard for someone to know where they should submit charm changes.
The text was updated successfully, but these errors were encountered: