We preserve the documented interfaces across versions. The auto-upgrade to
3.3 could only break your app if you are using undocumented interfaces. We
use versioning to give sites a few months to report bugs and double-check
their site against upcoming versions.

On Mon, Mar 7, 2011 at 9:56 AM, Steffen <[email protected]> wrote:

> So the answer would rather be "yes", since the auto-upgrade to 3.3
> could break my app, right?
>
> Like you said, I basically would have to check my apps with every new
> release (and my app gets auto-upgrade)? :-(
> What's the sense of the versioning then?
>
> I'd understand if you would deprecate/disable really old versions like
> from a few years ago, but a 6 months time span for disabling old api
> version seems to be very short.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google Maps JavaScript API v3" 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-js-api-v3?hl=en.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google Maps JavaScript API v3" 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-js-api-v3?hl=en.

Reply via email to