On Feb 13, 1:39 am, "pamela (Google Employee)" <[email protected]> wrote: > > Do the developers here feel that we shouldn't promote 2.145 to v2 next > week due to this bug?
The sticky post says "Yesterday, we pushed v2.145 as v2.x and kept v2.140 as v2, due to the multiple regression bugs that are still in 2.143. We expect to set v2 to 2.145 next week, when 2.146 is released as v2.x. Please let us know in the forum if you think there are any regression issues in 2.145 that should block that from happening." There are quite a few fixes in 2.145: but have the bugs in 2.143 which prevented the promotion of that version been fixed? If not, then those bugs should also mean that 2.145 doesn't get promoted. Having said that, the recently-introduced fault which meant infoWindows didn't avoid controls is supposed to be fixed in 2.145 and that is quite important. Could the changelog http://code.google.com/p/gmaps-api-issues/wiki/JavascriptMapsAPIChangelog also indicate in which version an issue was introduced? That would help with answering this sort of question. 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 -~----------~----~----~----~------~----~------~--~---
