Hey Andrew, Barry- The API release process isn't separate from the maps.google.com process right now, as they share the common codebase. Since the maps release process is on a one-week schedule, so is the API release.
When we test version 2.133 on a external URL the week before releasing (to make sure to catch problems that would only show up externally), we increment the letter of each test release. We had to introduce the release lettering in order to avoid the cache issue that the Australian developers had a few months ago (they were getting a testing version instead of the final release version, due to the aggressive cache there). We are looking into implementing version aliasing, but we're trying to do it in a way that will be the most beneficial to developers, particularly for when there are bugs discovered in a release or there are caching issues -- and doing that in the right way is taking time. Hope that's a bit more transparent. And if nothing else, we may have inadvertantly introduced bugs in this release, so knowing that a release has occurred should make debugging easier. - pamela On Mon, Oct 20, 2008 at 11:36 PM, warden [Andrew Leach - Maps API Guru] <[EMAIL PROTECTED]> wrote: > > On Oct 20, 9:34 am, "pamela (Google Employee)" <[EMAIL PROTECTED]> > wrote: >> >> There are currently no changes in 2.133d. > > So why make a new release? > > Anyway, if nothing's changed, shouldn't the next version be v2.133a? > > Andrew > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
