[vtk-developers] Meeting minutes

[Dave Partyka]

I have taken look at what is involved to do the sub-projects as there was
interest from the Slicer developers. The main pre-requiesite issue that
would need to be addressed is that vtk (ParaView) would require cmake-2.8,
which is probably a matter for Berk or the ARB to decide (?), especially
considering that we recently switched to requiring 2.6.3.

It might involve an alligment of the planets and a VTK release or two first
:-p

That said, I am responsible for all VTK/ParaView dashboards and I am
most definitely in favor of making use of this very cool feature! It
would definitely reduce the amount of email I get ;-)


> >
> > ==Dashboard division==
> > It would be nice to divide the VTK dashboard into sections (Graphics,
> > Filters, etc) using the new CDash functionality Bill Hoffman
> demonstrated.
> > This would alleviate the problem of receiving a dashboard error email
> every
> > time you commit something even if it has nothing to do with your change.
> *
> > Who* can implement this?
>
> I will hopefully talk to Bill about this soon. It sounds like the build
> system
> changes would not be too invasive, and should be ignored by older CMake
> versions. I think this would really improve the quality of the results from
> CDash. I could tentatively volunteer, dependent on finding out how much
> time
> would be involved in this change.
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/vtk-developers/attachments/20091217/7e526292/attachment.html>