Even the underlying code is guaranteed for the lifetime of the frozen version. If you work with the versioning system your site is protected from unexpected changes. On Mar 7, 2011 7:29 PM, "sgiddings" <mr.s.giddi...@gmail.com> wrote: > Wow, I wasn't expecting so many exchanges. > > From what I am seeing here, the only thing which is guaranteed with > versioning, are the interfaces. > The underlying code is not guaranteed - notably undocumented features > which a number of us have relied on. > > On Mar 7, 12:12 am, Ben Appleton <apple...@google.com> wrote: >> I'll reply in that thread. >> >> On Mon, Mar 7, 2011 at 10:09 AM, Steffen <steffen.hil...@gmail.com> wrote: >> > Ok, well, to be more specific, >> > here's the problem I have after the update: >> >> >http://groups.google.com/group/google-maps-js-api-v3/browse_thread/th... >> > It's something that as far as I see it is not working as documented >> > and I really don't know yet how to solve it. >> >> > Thanks for your quick responses & Google Maps! :) >> >> > On Mar 6, 7:01 pm, Ben Appleton <apple...@google.com> wrote: >> > > 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 <steffen.hil...@gmail.com> >> > 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 >> > > > google-maps-js-api-v3@googlegroups.com. >> > > > To unsubscribe from this group, send email to >> > > > google-maps-js-api-v3+unsubscr...@googlegroups.com. >> > > > 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 >> > google-maps-js-api-v3@googlegroups.com. >> > To unsubscribe from this group, send email to >> > google-maps-js-api-v3+unsubscr...@googlegroups.com. >> > 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 google-maps-js-api-v3@googlegroups.com. > To unsubscribe from this group, send email to google-maps-js-api-v3+unsubscr...@googlegroups.com. > 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 google-maps-js-api-v3@googlegroups.com. To unsubscribe from this group, send email to google-maps-js-api-v3+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-maps-js-api-v3?hl=en.
