Fwd: Upcoming changes: 3.11 becomes release version on Feb 15; changes to default version provided

[Enoch Lau]

---------- Forwarded message ----------
To: google-maps-js-api-v3-notify <google-maps-js...@googlegroups.com>

We will be making the current experimental version (3.11) the default version on or shortly after February 15, 2012. The versions will then be:

Experimental: 3.12

Release: 3.11

Frozen: 3.10

3.9 will be removed, and you will be provided with 3.10 if you request it.

At the same time, we will be making a change to the version provided by default (the version provided if you do not specify v= when loading the Maps API):

  - If you are using a Maps API for Business client ID, you will be provided with the release version by default.

  - If you are not a Maps API for Business customer, you will be provided with the experimental version by default.

Regardless of whether you are a Maps API for Business customer or not, you can add v=3 to always receive the current release version.

We encourage you to test your applications with 3.11 before February 15, which you can do by adding v=3.11 when loading the Maps API. If you like to live on the edge, you can add v=3.exp to always receive the current experimental version with all of its latest features.

For more information about Maps API versioning, see:

https://developers.google.com/maps/documentation/javascript/basics#Versioning

To report issues with any version of the API, see:

http://code.google.com/p/gmaps-api-issues/issues/list

[Barry Hunter]

Would be nice if us non-business customers could request "3.rel" to request the current release, especially for production environments.
- Doug

Whats wrong with

Regardless of whether you are a Maps API for Business customer or not, you can add v=3 to always receive the current release version.

 

??

[Enoch Lau (Google Employee)]

Yes, v=3 will work come Feb 15 to always request release.

[THE_AI]

I'm a little late to the party... sorry about that.
This bug over here:
http://code.google.com/p/gmaps-api-issues/issues/detail?id=4908
Since we cannot use v3.9 of the API anymore there is no way around the issue? Are developers supposed to use the default infowindow, or should we create our own Infowindows with custom overlays?