[Imstk-developers] Updating VTK version rules
Alexis Girault
alexis.girault at kitware.com
Wed May 10 17:57:00 EDT 2017
I'd agree with Dzenan, unless there is a stable release previous to latest
master. Also, there can be regressions sometimes, so we just have to make
sure that the rest works.
On Wed, May 10, 2017, 17:55 Dzenan Zukic <dzenan.zukic at kitware.com> wrote:
> It is best to update to the most recent release, unless that is not new
> enough. In that case it is probably best to update to master.
>
> Dženan Zukić, PhD, Senior R&D Engineer, Kitware (Carrboro, N.C.)
>
> On Wed, May 10, 2017 at 5:37 PM, Milef, Nicholas Boris <milefn at rpi.edu>
> wrote:
>
>> I need to update VTK to at least:
>> fd8bfb599d9fb78cd6589363bd717d3f1007d22b
>>
>> because of VBO related features. What's the general rule to this, should
>> I update to the most recent version/commit of VTK or just this commit?
>>
>> _______________________________________________
>> Imstk-developers mailing list
>> Imstk-developers at imstk.org
>> http://public.kitware.com/mailman/listinfo/imstk-developers
>>
>>
> _______________________________________________
> Imstk-developers mailing list
> Imstk-developers at imstk.org
> http://public.kitware.com/mailman/listinfo/imstk-developers
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/imstk-developers/attachments/20170510/f4b18bd0/attachment.html>
More information about the Imstk-developers
mailing list