Thanks, Larry. It's current now. I'll make that change first in the future.
FYI, it's likely that this is how we'll continue to do v2 changes in the future. Instead of the old way where v2 changed at the same time as v2.x, we'll release the new 2.x and then wait a day or two before we set v2. Or in the case where v2 contains regression bugs, we simply won't change it that week. - pamela On Tue, Mar 24, 2009 at 11:42 PM, [email protected] <[email protected]> wrote: > > On Mar 24, 5:33 am, pamela fox <[email protected]> wrote: >> We've now changed v2 from 2.148 to 2.150. >> >> The changelog has information about what's changed in >> 2.150:http://code.google.com/p/gmaps-api-issues/wiki/JavascriptMapsAPIChang... > > The changelog still lists v2.148 as "current". Is it up to date? > > -- Larry > > >> >> As always, please discuss anything in the forum >> (http://groups.google.com/group/Google-Maps-API/) that you think may >> be a regression and report it in the issue tracker if others confirm >> your suspicions. > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
