The Google Chart Tools team has pushed a new release candidate

[Jinji]

If your system uses the Visualization API for commercial and / or important production purposes we recommend you test the RC and use the opportunity to provide feedback to us prior to the production release. If there are any issues, these can be communicated back to our team by replying to this message.

Enjoy, 
The Google Chart Tools team

[NA]

Can you post a changelog so we know what to look for?

Without a changelog, it becomes very difficult to verify that the RC
is good unless the application built with it is relatively trivial.
Verifying that the RC works with more complex applications requires
that we have some idea what to look for, since doing an exhaustive
test on a large app can be very time consuming.

thanks!

[Jinji]

I understand that, but we regularly make changes to all parts of the code, so it's really hard to make such a list (remember that such a list would only contain changes to existing feature, not new features; those will be announced only after their implementation + documentation is complete)

That said, we do want to mention some changes to GeoChart. This release contains some changes to GeoChart which were made in order to improve the default behavior of it. We're sorry if those cause any inconvenience, but we believe that are worth it in the long run.

• Region interactivity in marker mode is now disabled by default.
  How to keep the old behavior? Set the enableRegionInteractivity option to 'true'.
• Markers are now opaque by default.
  How to keep the old behavior? Set the markerOpacity option to 0.5.
• Marker size is now between 3 and 12 pixels by default.
  How to keep the old behavior? Set the sizeAxis option to  {minSize: 2, maxSize: 30}.
• A magnifying glass is now opened when the user hovers over cluttered markers.
  How to keep the old behavior? Set the magnifyingGlass option to {enable: false}.
• We don't stretch the maps by default anymore, but rather keep the original aspect ratio.
  How to keep the old behavior? Set the keepAspectRatio option to 'false'.

--
You received this message because you are subscribed to the Google Groups "Google Visualization API" group.
To post to this group, send email to google-visua...@googlegroups.com.
To unsubscribe from this group, send email to google-visualizati...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-visualization-api?hl=en.

[NA]

Nah, it's not hard at all. As you make a change, put it in a list.
That's a good start, and isn't difficult. A product manager or
interested individual can review the list to make it more customer
friendly, though that's not really necessary if you don't have the
resources. Then you post the list. Customers like me read it or
ignore it, depending on whether we'd like more information or to
maintain the status quo.

If you want to only include changes to existing features, that's
perfectly fine. In fact, for managing change risk, that's probably
all we need.

Changelogs are even especially important because the GVIZ product
doesn't follow Google's versioning policy. The reliability risks with
each GVIZ release are high. Changelogs let us identify that risk.