> It is not just about JOSM, the change breaks *every application, web service or browser plugin* that creates a reference to the osm main page or that could parse an OSM url.
Links to the homepage are backwards-compatible. We've set up redirects. > No. If you just go ahead with changes that break things, you should anticipate damage reports. Bug reports are fine, and expected. I'm not asking for silence: I'm asking for less editorializing, hyperbole, and negativity. On Thu, Aug 8, 2013 at 10:33 AM, NopMap <[email protected]> wrote: > tmcw wrote > > Is it really a terrible weight to update JOSM to recognize the new > format? > > It is not just about JOSM, the change breaks *every application, web > service > or browser plugin* that creates a reference to the osm main page or that > could parse an OSM url. > > That's a little bit more :-). > > What's more as this was done unannounced (no, an internal issue tracker is > not an announcement), all these applications are failing now as a surprise > for their users. > > > tmcw wrote > > Can we stop calling any feature that changes the behavior of the site "a > > major step backwards"? > > No. If you just go ahead with changes that break things, you should > anticipate damage reports. > > Maybe a wider discussion of the expected impacts could have avoided the > problem, but asking for silence on the topic will neither fix the problem > nor the (lack of) procedure which created it. > > bye, Nop > > > > > -- > View this message in context: > http://gis.19327.n5.nabble.com/The-new-link-on-the-OSM-map-tp5772913p5772979.html > Sent from the Developer Discussion mailing list archive at Nabble.com. > > _______________________________________________ > dev mailing list > [email protected] > http://lists.openstreetmap.org/listinfo/dev >
_______________________________________________ dev mailing list [email protected] http://lists.openstreetmap.org/listinfo/dev
