Maps API v3.2 being retired (was: 2011/5/7 - New Release (3.5))

[Chris Broadfoot (Google Employee)]

Just to follow up on my mail from a couple weeks ago (copied below), we'll be retiring v3.2 today.

In accordance with our versioning strategy, any sites requesting version 3.2 will receive 3.3 instead (the new frozen version).

I'll take this as an opportunity to remind you to always test your map against nightly version (now 3.5) so that we can catch any issues early in the release cycle.

Chris

---------- Forwarded message ----------
From: Chris Broadfoot (Google Employee) <c...@google.com>
Date: Sun, May 8, 2011 at 5:53 AM
Subject: 2011/5/7 - New Release (3.5)
To: "google-map...@googlegroups.com" <google-map...@googlegroups.com>

Hi all,

We're pleased to announce version 3.5 of the Maps API for JavaScript.

Firstly, a reminder that if you do not specify a minor version when loading the Maps API, you will automatically receive 3.5. Production applications should always specify a minor version (v=3.3, v=3.4). Read more about versioning here:

http://code.google.com/apis/maps/documentation/javascript/basics.html#Versioning

We plan to retire 3.2 on May 15, and applications that request 3.2 will receive 3.3. At this time, 3.3 will be frozen, and no further code changes will be made.

3.5 includes all changes for 3.4. You can see the full change log here:

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

This release is essentially identical to the latest 3.4 release, and no features have been added.

--
http://twitter.com/broady

--
http://twitter.com/broady