Hi Patrick,
V45 was actually rolled out, which I mentioned in my May 9 comment. This
was only a release on the old jsapi server. You are correct that we
neglected to add to the release notes, but I was waiting until I could
finish rolling out to the new gstatic server. But now that has been
deferred a bit, because of the following.
Since that rollout, one serious bug came up on May 9, and another became
apparent at the end of May. Since I have fixes for those bugs, I will
update V45 before proceeding with the gstatic update.
Any changes we make to the gstatic server do not affect anything on the
jsapi server, at least not yet. We plan to eventually redirect all
requests on the jsapi server over to the gstatic server, once we have
finished implementing all the loader features. There will be a big
announcement when that happens.
The new gstatic loader is slightly slower because of the sequential loading
that is imposed. We were being overly cautious, however, and we should be
able to speed that up at some point.
On Wed, Jun 1, 2016 at 4:30 PM, Patrick Walker <pataw...@gmail.com> wrote:
> So has V45 "officially" been released? When does it go to current? I don't
> see it at the below link. Also,we use the old loader
> (google.load("visualization",1,...etc). When this new version goes to
> "current" how will this affect those loading the old way? Part of the
> reason we haven't switched to the new loader is that it seems to load a
> little slower. Thanks
>
>
> https://developers.google.com/chart/interactive/docs/release_notes#release-candidate-details
>
>
> On Tuesday, April 26, 2016 at 12:10:32 PM UTC-5, Daniel LaLiberte wrote:
>>
>> We are about to push a new Google Charts Production Release - *V45*.
>>
>>
>> Previously we announced the Release Candidate on April 7 here:
>> https://groups.google.com/forum/#!topic/google-chart-api/eMOR1jsS6No
>>
>>
>> The production release was delayed until now because we were trying to
>> work around a problem, but we were unsuccessful. However, it turns out
>> this problem (which was displaying more than one Material chart in the same
>> page) also existed in the previous release (v42) so this new release will
>> not be any worse than that. If you need this fixed, please try frozen v43
>> or v44.
>>
>>
>> The purpose of this push is to update the old jsapi-loaded library with a
>> version that is close to the previously released v44. We are doing this
>> primarily to incorporate some security fixes that are already part of v44
>> into the jsapi loaded release, and as such, there are very few
>> additional bug fixes and these are unlikely to be visible to people.
>>
>> The last time we were successful updating the old jsapi loaded library
>> was for v42. So if you are still using that version of the code, you
>> should look at the release notes for v43 (
>> https://developers.google.com/chart/interactive/docs/release_notes#october-2-2015)
>> and v44 (
>> https://developers.google.com/chart/interactive/docs/release_notes#february-23-2016)
>> to see what has changed.
>>
>> There are still many pages out on the web using the old jsapi loader, and
>> these will be affected by this update. Recall that the library was loaded
>> like this:
>>
>> google.load('visualization', '1' (or '1.0' or '1.1), { packages: [...]
>> });
>>
>> If your pages load the library this way, you will be affected by this
>> production release.
>>
>> If you have problems with this production release, you may want to
>> switch to loading the frozen v42, so your code will look like this:
>>
>> <script type="text/javascript"
>> src="https://www.gstatic.com/charts/loader.js";></script>
>> <script type="text/javascript">
>> google.charts.load('42', {packages: ['corechart']});
>> google.charts.setOnLoadCallback(drawChart);
>> </script>
>>
>> We recommend switching to the 'current' version instead of '42' using the
>> new loader if you can, so you will see future updates.
>>
>> We will update the frozen version v45 soon to match this production
>> release.
>>
>> --
>> Daniel LaLiberte <https://plus.google.com/100631381223468223275?prsrc=2>
>> dlali...@google.com 5CC, Cambridge MA
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Google Visualization API" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-visualization-api+unsubscr...@googlegroups.com.
> To post to this group, send email to
> google-visualization-...@googlegroups.com.
> Visit this group at
> https://groups.google.com/group/google-visualization-api.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-visualization-api/1701d611-de53-4845-ba71-8c191ae01e7c%40googlegroups.com
> <https://groups.google.com/d/msgid/google-visualization-api/1701d611-de53-4845-ba71-8c191ae01e7c%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>
--
Daniel LaLiberte <https://plus.google.com/100631381223468223275?prsrc=2>
dlalibe...@google.com <dlalibe...@google.com> 5CC, Cambridge MA
--
You received this message because you are subscribed to the Google Groups
"Google Chart API" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to google-chart-api+unsubscr...@googlegroups.com.
To post to this group, send email to google-chart-api@googlegroups.com.
Visit this group at https://groups.google.com/group/google-chart-api.
For more options, visit https://groups.google.com/d/optout.
