First one: publish the plugin now and mark it as dependent of the minimum
JOSM development version. Plugins don't have to care about of JOSM being
tested or latest: they just have to reference the minimum compatible
version.
Le mer. 31 oct. 2018 à 15:14, allierosm a écrit :
> just to clarify my
just to clarify my question:
Would it make sense to publish the plugin now and mark it as dependent
of a JOSM development version, or rather wait until the next JOSM
milestone is released and then publish the plugin?
Le 31/10/2018 à 13:37, allierosm a écrit :
Hello,
I have made a
Hello,
I have made a pre-release available:
https://github.com/JOSM/strava_heatmap/releases/tag/v0.9
There is an open issue (https://github.com/JOSM/strava_heatmap/issues/2)
and the fix will require an enhancement that is planned for the next
JOSM milestone
Done :-)
Le 30/10/2018 à 13:09, Vincent Privat a écrit :
I have invited you to the organization. Then we must follow this
procedure:
https://help.github.com/articles/transferring-a-repository-owned-by-your-personal-account/#transferring-to-an-organization
Le mar. 30 oct. 2018 à 12:40,
I have invited you to the organization. Then we must follow this procedure:
https://help.github.com/articles/transferring-a-repository-owned-by-your-personal-account/#transferring-to-an-organization
Le mar. 30 oct. 2018 à 12:40, allierosm a écrit :
> Hello,
>
> Sure, I can move the plugin
Hello,
Sure, I can move the plugin repository to the Github JOSM organization,
just let me know how to proceed.
Le 29/10/2018 à 21:29, Vincent Privat a écrit :
Thanks! I have added a new Trac component "Plugin strava_heatmap" and
set you as maintainer.
I have reaffected #16100 to this new
Thanks! I have added a new Trac component "Plugin strava_heatmap" and set
you as maintainer.
I have reaffected #16100 to this new plugin.
I see your plugin defines strings to be translated. Would you like to bring
this new plugin to the Github JOSM organization? This way it's easier for
everyone
