We've deliberately chosen not to implement a versioning scheme in v3 while it is in Code Labs, because we want as many users as possible banging on the latest version so that bugs are identified quickly, and we want to avoid being required to maintain interfaces we need to change any longer than necessary.
We recognise that we'll need a versioning scheme once the API has matured to the point we are happy blessing v3 for use in change sensitive environments (like Enterprise sites) and are working out the details, but for the time being we'd like to stay light on our feet. As Ben says, we'll be sure to announce when versioning is in place on this group, so stay tuned. Thor. On May 13, 9:40 pm, Nick Smith <[email protected]> wrote: > Any chance of making a 'more stable' version of v3 available, like > there is for API v2 ? Even if it was just delayed by a couple of > weeks, that would be enough to catch most serious issues, and it would > mean we could develop without being exposed to the bleeding edge > version, if that was what we wanted. > > (The issue with MarkerClusterer had me tearing my hair out for a > couple of hours before I realised there was a new version of v3 that > was causing the problems!) > > Many thanks > > -- > 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 > athttp://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.
