google / google-visualization-issues

288 stars 35 forks source link

allow developers to fix on a specific google viz library version, rather than forcing upgrades #120

Open orwant opened 9 years ago

orwant commented 9 years ago
What would you like to see us add to this API?

There is always a risk that a new version of the library could introduce a
regression (as the most recent release did, in that hovers no longer work
in IE8 in IE7 compatibility mode).  While it is great that google is
providing release candidates for early testing, it would be even better if
google could simply retain a few (2 or 3?) versions of the library so that
developers could fix their code to run against a particular version and
then not have to worry that a new version would break existing
functionality.  A 6 month deprecation policy (or the like) would be
extremely helpful, and would give developers more confidence in being able
to use google viz in production environments.

What component is this issue related to (PieChart, LineChart, DataTable,
Query, etc)?

*********************************************************
For developers viewing this issue: please click the 'star' icon to be
notified of future changes, and to let us know how many of you are
interested in seeing it resolved.
*********************************************************

Original issue reported on code.google.com by bridget.frey on 2009-11-13 18:04:07

orwant commented 9 years ago
This version control is very important to serious users of your API, who cannot manage
a product without it.  Additionally, this would make the Visualization API consistent
with other Google APIs.  

For a discussion on this issue, see:

 http://groups.google.com/group/google-visualization-api/browse_thread/thread/2153b62cdb4c54c6

To see the Google API standards on this, see:

  http://code.google.com/apis/libraries/devguide.html#versioning

Original issue reported on code.google.com by nabeel.azar on 2011-06-29 20:23:30

orwant commented 9 years ago
Issue 800 has been merged into this issue.

Original issue reported on code.google.com by jinji.viz on 2012-06-19 15:04:43