On Feb 14, 1:52 pm, "Neil.Young" <[email protected]> wrote: > what the best strategy for version choice for users might > be. Is it a good idea to choose "v=2" in alive environment? Or is it > better to choose those version explicitly, which is "v2" the time, one > creates and tests his map, e.g. "v=2.140"? The fatal drawback of "v=2" > (from my POV) is the fact, that a stable customer solution might become > instable or even stop working, because Google may brake some features in > future "v2s" or may depreciate some things. The questions for a > "v=2.140" approach would be: How long will that live? And is it > guaranteed, that 2.140 is never changed after published once?
All versions below v2.s have been aliased to v2.s (currently v2.73). When v2.s goes above v2.140, any pages that explicitly call out v2.140 will end up using v2.s. Other than that, the existing v2.140 code shouldn't be modified, but changes in the loader behavior could effect it (like the erroneous removal of the v1 map types last October) The best strategy: Use v.2 for production sites unless there is a bug in it that effects your map. Then use the most recent version that works and "star" the bug (obviously report it if hasn't been already). When the bug is fixed go back to v2. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Maps API" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/Google-Maps-API?hl=en -~----------~----~----~----~------~----~------~--~---
