Open Malvoz opened 4 years ago
When reviewing TomTom, I noticed v5 was listed as being under public preview and that breaking changes were possible, which is why I opted to go with v4. I definitely support reviewing latest versions, but should this include latest 'unfinished' versions?
I'll see about updating the existing examples (along with those in development) for OpenLayers, but leave the TomTom examples on v4 while v5 remains in preview.
Agreed. When we are finalizing the report for publication, we'll probably do a final review including identifying any updates in the tools that might affect conclusions. But I'm not going to tear everything out every time a minor version gets bumped up.
However, if the recommended CDN is shutting down, that's definitely something we need to fix, so might as well do an update at the same time.
FWIW, TomTom’s v5 is now generally available, with v4 reaching end of support in January 2021.
RawGit is shutting down, and OpenLayers has shifted to using jsdelivr instead.
So we'll have to update the linked resources, and I propose using the latest version (which will need testing):
I also propose we use the latest version of resources for all the reference tools, because it wouldn't be fair/accurate to assess older versions of a tool.
Obviously, it'd take a lot of work to continuously update resources for all the reference tools and to also update the assessments based on a particular version, but I think we should consider updating resources at least once for now - as we seem to be using quite outdated resources in some cases (e.g. for CSS/JS we're using MapBox
v1.0.0
while latest isv1.3.2
, or TomTomv4.47.6
while latest seem to bev5.36.1
)./cc @AmeliaBR, @nchan0154, @NickFitz for thoughts.