[vtk-developers] heads up - vtk 5.10 branch is coming soon

[Julien Finet]

Indeed, ideally we would need to wait until Monday. However, if you prefer,
I can submit the API change now, with a slight risk of a patch later (not
likely to be an API change)
That way, Slicer 4.1 (feature freeze on Monday) will be build with VTK 5.10
(and not a custom VTK version special for Slicer).

Let me know,
j.

---------- Forwarded message ----------
From: Julien Finet <julien.finet at kitware.com>
Date: Wed, Feb 22, 2012 at 9:25 AM
Subject: Re: [slicer-devel] Slicer4 and VTK version
To: Will Schroeder <will.schroeder at kitware.com>
Cc: Michael Jeulinl <michael.jeulinl at kitware.com>


Hi Will,

I remember Michael had some commit reviews on hold in VTK
http://review.source.kitware.com/#/c/2992/   -> your initial commit
http://review.source.kitware.com/#/c/2993/   -> his re-work on it

However from the email discussion of 09/30/11, it seems that 2993 might not
be the most up-to-date code.
I guess the most up-to-date is what's in Slicer:
your initial work:
https://github.com/Slicer/VTK/commit/55e9b3d3e833a5890486495028f9fa725bb89296
Michael's rework:
https://github.com/Slicer/VTK/commit/6d2e956ade664c951ebc49496b01c230221a87fd
merge commit:
https://github.com/Slicer/VTK/commit/b8c6adc067b8ecfea65d9797338868b3a0b874ea

Michael being on vacation this week, it might be risky to push in VTK (just
as I'm not sure 100% sure of what is "current").
However, I believe what's in Slicer is pretty close to the last commit. So
you can definitely review it.

Thanks,
Julien.


On Sat, Feb 25, 2012 at 5:50 PM, Marcus D. Hanwell <
marcus.hanwell at kitware.com> wrote:

> On Thu, Feb 23, 2012 at 3:45 PM, David E DeMarle
> <dave.demarle at kitware.com> wrote:
> > Hey everybody.
> >
> > We are about to start the vtk5.10 release cycle. We would like to
> > branch as soon as this coming weekend - but if there are features out
> > there that are currently in progress and which are nearly finished, we
> > could delay a week or two for you to get them cleanly into master
> > before the branch happens.
> >
> > So, if you are currently working on features that you want to get into
> > this release, please reply all to this email and let us know what the
> > feature is and where you are at with it so we can plan accordingly.
> >
> The dashboards had a compile failure on them today (already reviewed
> and merged the fix), and I have several API changes and compile fixes
> I would like to get in. Julien Finet also let me know that there is a
> fix they are hoping to get in for Slicer, but the earliest it would be
> ready is Monday. My fixes are ready to go in once they have been
> reviewed. I am adding a Clang 3.0 Linux nightly submission to catch
> future issues with Clang on Linux.
>
> Thanks,
>
> Marcus
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/vtk-developers/attachments/20120225/60b5139e/attachment.html>