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

[Utkarsh Ayachit]

John,

A patch release before June sounds fairly reasonable.

Utkarsh

On Thu, Mar 18, 2010 at 5:49 PM, Biddiscombe, John A. <biddisco at cscs.ch> wrote:
> If you can 'promise' that 3.8.2 will come before June, then I'm happy. If not, then I'll just have to do my own unofficial releases with dodgy startup screens where paraview gets overlaid with some extra text etc etc!
>
> JB
>
>> -----Original Message-----
>> From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com]
>> Sent: 18 March 2010 22:20
>> To: Berk Geveci
>> Cc: Biddiscombe, John A.; paraview-developers at paraview.org
>> Subject: Re: [Paraview-developers] Moving to hdf5-1.8.x
>>
>> That sounds reasonable. Does that work John?
>>
>> Utkarsh
>>
>> On Thu, Mar 18, 2010 at 5:05 PM, Berk Geveci <berk.geveci at kitware.com>
>> wrote:
>> > Can we target the next patch release (3.8.2 I guess) for this? It will
>> > be 3 months (or less) after the 3.8 branch.
>> >
>> > -berk
>> >
>> > On Thu, Mar 18, 2010 at 4:22 PM, Utkarsh Ayachit
>> > <utkarsh.ayachit at kitware.com> wrote:
>> >> John,
>> >>
>> >> I understand your pain :), but this is just too late to commit such a
>> >> (arguably) major change. We are planning on a CVS freeze come Tuesday
>> >> and a branch on Friday. Besides it's only a matter of few months
>> >> before the next official release of ParaView, so you can soon tell
>> >> your users that yours plugins will work against an official release.
>> >>
>> >> Utkarsh
>> >>
>> >> On Thu, Mar 18, 2010 at 4:10 PM, Biddiscombe, John A. <biddisco at cscs.ch>
>> wrote:
>> >>> 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
>> >>>> >
>> >>> _______________________________________________
>> >>> Paraview-developers mailing list
>> >>> Paraview-developers at paraview.org
>> >>> http://public.kitware.com/mailman/listinfo/paraview-developers
>> >>>
>> >>
>> >
>