[vtk-developers] IMPORTANT: Attribute data changes (vtkScalars, vtkVectors etc)

[David Gobbi]

Hi Berk, Prabhu,

I'm kinda with Berk on this one.  We really can't judge his changes
until he commits them and we have a chance to try them out.  At that
point, the worst backwards compatibility issues can be worked out and,
if too many things break, the changes can be backed out temporarily.

Making a VTK 4.0-pre release would require someone to do a fair bit
of work.  I think that a CVS tag would be sufficient, since all the
current VTK-4 users are grabbing VTK from cvs anyway.  I think that it
is best to have no releases whatsoever until the code is ready
for a beta release, and the beta release should come after any
major structural changes have been integrated.

 - David

--
  David Gobbi, MSc                       dgobbi at irus.rri.ca
  Advanced Imaging Research Group
  Robarts Research Institute, University of Western Ontario

On Thu, 11 Oct 2001, Prabhu Ramachandran wrote:

> Hi,
>
> >>>>> "BG" == Berk Geveci <berk.geveci at kitware.com> writes:
>
>     BG> VTK 4.0 is coming. If I don't do this by November 1st, there
>     BG> will not be enough time to test the changes. Putting warning
>     BG> messages is not enough because things can be missed if the old
>     BG> code is still functioning. I know this because, although I was
>     BG> trying to keep things functioning, when I removed the classes
>     BG> from my local build, a lot of things broke.  Also, people keep
>     BG> adding code which use vtkScalars etc. I have been maintaining
>     BG> a separate VTK for a long time (I started making these changes
>     BG> almost 8 months ago) and I want to be able to merge all my
>     BG> changes at least a month before 4.0 is close to be released.
>
> I understand, then if possible, how about making sources and binaries
> of VTK 4.0-pre before doing this and delaying things a bit.  I can
> manage to get around this problem myself.  But it really would be a
> good idea to make things easier for the users and others.  You really
> cant expect everyone to access VTK off CVS and then get Cmake too off
> CVS and then build both etc. Dont you folks think so?
>
> This is just a request.  No hard feelings. :)
>
> prabhu
> _______________________________________________
> vtk-developers mailing list
> vtk-developers at public.kitware.com
> http://public.kitware.com/mailman/listinfo/vtk-developers
>