On Jul 19, 10:13 am, Pil <[email protected]> wrote: > Hmm, maybe you are right. But then it's on principle impossible to > spcecify any precise version like in v2. > > No good idea in my eyes....
The versioning seems much less mature in v3 than it was in v2. It doesn't seem ready for production websites. -- Larry > > On Jul 19, 6:43 pm, "[email protected]" <[email protected]> > wrote: > > > > > On Jul 19, 9:07 am, Pil <[email protected]> wrote: > > > > Versioning as documented here > > > >http://code.google.com/apis/maps/documentation/javascript/basics.html... > > > > doesn't load the version of the API which is specified. For example > > > this request > > > > <script type="text/javascript" src="http://maps.google.com/maps/api/js? > > > v=3.1.6&sensor=false"> > > > </script> > > > > doesn't load v3.1.6 but I always get 3.1.7a instead. > > > That documentation says: > > > > Documentation of Versions > > > Documentation will always reflect the latest (development) version. > > > However, for each version, we will offer a > > > separately maintained reference. > > > Latest Version (3.1) Reference (Current) > > > Release Version (3.0) Reference (Feature-stable) > > > So I don't think the third digit works. You are asking for 3.1 (the > > latest release) and getting the latest release. The only other option > > is 3.0 which as I recall is fairly old. > > > -- Larry- Hide quoted text - > > - Show quoted text - -- 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.
