[Paraview-developers] Moving to hdf5-1.8.x

[Biddiscombe, John A.]

It is a big change conceptually speaking, but there are few places that are actually using it in paraview - a handful of readers and that's about it really.

I am trying to kill pv-meshless off and use only plugins, but unless I upgrade paraview cvs, I need to maintain my own version - which will be easier with git, but not as nice as telling people that 3.8 is compatible. (also, paraview 3.8, hdf 1.8 - see how they rhyme. It's almost like they belong together).

JB



> -----Original Message-----
> From: Berk Geveci [mailto:berk.geveci at kitware.com]
> Sent: 18 March 2010 21:02
> To: Biddiscombe, John A.
> Cc: paraview-developers at paraview.org
> Subject: Re: [Paraview-developers] Moving to hdf5-1.8.x
> 
> Ah, I see. I didn't realize that you wanted it in 3.8. That's
> Utkarsh's call. Making such a big change  (is it big? I am guessing
> so) 1 week before branch is a bit risky. I'd suggest checking it in
> after 3.8, let it mature for a few months and have it be official in
> 3.10 (or 4.0 whatever it is called).
> 
> -berk
> 
> On Thu, Mar 18, 2010 at 3:36 PM, Biddiscombe, John A. <biddisco at cscs.ch>
> wrote:
> > Berk
> >
> >> I vote for (2). I also vote for waiting until after we branch 3.8 and
> >> after we switch to Git (which will follow the 3.8 branch by a week or
> >> two). In all, it will probably be around 4 weeks before we switch to
> >> Git.
> >
> >
> > As long as I can get it into 3.8 - then I will be happy to wait for git
> etc.
> >
> > JB
> >