[josm-dev] JOSM releases

[Frederik Ramm]

Hi,

> BTW: Concerning plugins: I don't think that the former "works with JOSM 
> 1.5" wiki page imi tried out is the way to go. A JOSM release should 
> contain a snapshot of the available plugins as well, this way makes it 
> much easier for users to get a set of JOSM and plugins that probably 
> will work together. This versioning of plugins is currently a PITA and 
> doesn't really work IMHO.

The whole auto-update thing is a bit broken, or at least tends to
break in the hands of stupid people like me. Several plugin ant files
seem to automatically use the SVN revision as their version - not
the *latest* revision, but the latest revision to affect the plugin. I
updated a plugin, did "svn update", it said "at revision 1234", I
updated the plugin page to say "revision 1234", but in fact the plugin
build hat somehow decided that revision 1211 is applicable to the
plugin, which led to JOSM constantly trying to download...

Also, the plugins overview page in JOSM has me constantly puzzled as
to what the buttons actually mean. 

> What I would like to see is to have a JOSM jar file that contains all 
> plugins that were current at the time it was build (which plugins are 
> enabled by default is a different question/discussion).

Not the worst idea perhaps. 

> In the end, anything other than taking a snapshot of the current trunk 
> and release that won't work IMHO.

But that would mean that, with a fixed release schedule of "1st of
each month" or so, nobody would dare to add hot new features during
the last few days of a month (or in fact nobody SHOULD do that, lest
the whole idea of having stable vs unstable is only hot air).

Bye
Frederik

-- 
Frederik Ramm  ##  eMail frederik at remote.org  ##  N49°00.09' E008°23.33'