Silly group innit ;) Anyways, i applaude 2.s being stable but bit more recent. Imo a good version to lock production sits on.
2008/9/4 pamela (Google Employee) <[EMAIL PROTECTED]> > > Excuse my strange spewing of posts; groups apparently wouldn't let me > post a new thread with the exact same title. > > On Sep 4, 2:16 pm, "pamela (Google Employee)" <[EMAIL PROTECTED]> > wrote: > > -- This has been reposted so that the suggested guidelines post > > appears at the top of the forum -- > > > > Hi developers- > > > > As some of you know, we release a new version of the API javascript > > every 1 to 2 weeks. We have 3 version aliases - 2.x, 2, and 2.s. When > > you request v2.x, you're getting the very-latest version - you > > generally do this if you want to test bug fixes or try out newly added > > features. When you request v2 (the recommended version alias), you're > > getting the next-to-latest version. When you request v2.s, you're > > getting the 'stable' version - meaning a version that doesn't have any > > bad bugs but also won't be updated very frequently, so it's good for > > developers who don't want to worry about newly introduced bugs as we > > update each version. The currently served versions are 2.123 for 2.x, > > 2.122 for 2, and 2.73 for 2.s. When we find a version that doesn't > > have any major bugs (unfortunately this takes a while to find), we'll > > upgrade v2.s to a more recent version. > > > > Because we'd like to focus our testing and efforts on supporting the > > latest and greatest versions of the API - but also because we want to > > make sure that there is a version that each developer can use that > > fulfills their features but doesn't have app-effecting bugs - we've > > decided to stop serving javascript versions less than 2.s. This means > > that when a developer requests, for example, 2.72, they'll actually > > get served 2.73. We've introduced the global constant G_API_VERSION to > > make it easy for developers to see what version they're being served. > > We're fairly certain that this automatic upgrade shouldn't break a > > significant number of sites using the lower version numbers, as we've > > checked both the logs and the logged bugs and found that there aren't > > many sites using the lower versions, and there aren't many bugs in the > > lower versions that aren't fixed in 2.73. > > > > I know we haven't been clear about our policy in the past about > > supporting old versions - mostly because we weren't sure if it was > > feasibly to eternally support them or not. Now we've discussed it and > > realized it will be in the long run better for developers and our team > > to gradually fade out unnecessary versions and focus on more recent > > ones. > > > > The automatic upgrade will begin happening in a month (about 4 > > versions from now). Those of you who are using a version lower than > > 2.73 can change your code to using 2.s or 2 (or something in between) > > to test if everything's still working. Post in the group if you need > > help with the upgrade (with a link to your code, of course). > > > > Thanks, and let me know if you have questions. > > > > - pamela > > > -- Bjorn Brala ---------------- Google maps - Swis Webdesign --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
