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. -- You received this message because you are subscribed to the Google Groups "Google Visualization 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-visualization-api?hl=en.
