Hi Tom- You're correct, I did say that. That was a few months into my role here, and I've since learned better. In cases where there are, for some reason, issues with the version that "2" aliases to, I now advise developers to hard-code to a version number. I know some developers who, in fact, always hard-code to a version number, and that works better for them. As long as the version number is greater than 2.s (and we will notify if that is upgraded), then that version will still exist.
You're also correct that the API updates section doesn't warn strongly enough against "2.x"; we'll make that clearer. Perhaps even add some red text. We do actually do full testing against the 2.x release (since that's what maps.google.com uses), but in this case, there was a difference between the version we tested it against (no logging enabled) and the live version (logging enabled). We're remedying that for upcoming releases. FYI - I've also set a filter so that all of Mike William's "syntax changes" posts arrive directly in my inbox, so I can look into any issues he reports immediately. - pamela On Fri, Apr 3, 2009 at 7:28 AM, Tom NY <[email protected]> wrote: > > Hi Pamela, > > I just wanted to remind you that two years ago, a change to the v=2 > version broke the maps and you were recommending that people switch to > v=2.x > > > http://groups.google.co.in/group/Google-Maps-API/browse_thread/thread/bd9b7fd567054894/bf0d0a5106b64db0?lnk=gst&q=specifying+version#bf0d0a5106b64db0 > > "For the time being, could you change your code to use v=2.x? There > are no known errors with the latest version." > > Those are very scary words for a production IT department. That is > why I think it is important that the notify group provide warning of > all changes. I assume that versions like 2.x are release candidates > and having the ability to test them before they are actually released > can save us a lot of headaches even if we aren't using them as our > production version. Being notified that 2.155 has just been released > as v2.x means I can point my QA version to 2.155 and make sure that if > it does go live that I will have no problems. And being notified > ahead of time about a new v2 release means I can be sure that > resources are used to test that release before it is released. > > If you think about it from our POV, we have tens of thousands of > people relying on the maps that we have created using the Google Map > API. We just want to have the opportunity to make sure that any > changes you make don't break something we did (either through a > mistake on your part or our part). > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
