I was too busy at the Web 2.0 Expo last week that I missed this incident and discussion.
Fortunately I hard coded all my Google map apps to a stable version and did not notice nor affected by it. Case & point not to rely on 2.x - could not check and test for 2.x everyday! Btw I noticed Mike William (our super hero) forewarning week before the 2.x / 2.152 release. http://groups.google.com/group/Google-Maps-API/browse_thread/thread/9afc19e22dfbb9ad/a08869b2ab9be54c?lnk=gst&q=v2.152#a08869b2ab9be54c It helps to follow Mike's posting. ~newton On Apr 1, 2:34 pm, pamela fox <[email protected]> wrote: > As noted in the previous message, release 2.152 (2.x) contained a fatal bug > for API sites. That release has now been reverted, so using 2.x will load > 2.151 and using 2 will load 2.150. > Please take this opportunity to make sure that your production-level sites > are not using v=2.x of the API. > > You can read more about our API updates system in the > documentation:http://code.google.com/apis/maps/documentation/#API_Updates > > Barry Hunter has also written a good description of how the version > parameter > works:http://groups.google.com/group/Google-Maps-API/web/javascript-maps-ap... --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
