[Bf-committers] Aligning with the vfx reference platform in 2020

[Brecht Van Lommel]

I've updated https://developer.blender.org/T68774 with details on libraries
to upgrade and a patch.

On Sun, Jan 12, 2020, 04:34 Ray Molenkamp <ray at lazydodo.com> wrote:

> tbbmalloc proxy was failing on win10 on earlier versions of TBB, I forgot
> the exact
> version that fixed the issue [1] seems to imply it was 2019_U1, I bumped
> it to
> 2019_U9 just because it was current at the time, U6 will probably work,
> however
> I'm currently more interested in bumping the deps we have, rather than
> rolling back the
> one that is slightly ahead, given at-least one of them fixes some CVE's
> (openEXR).
>
> However as a platform dev I'm mostly following in the libs department, if
> someone
> tells me we need lib X version Y, I'll will go out of my way to make it
> happen
> however these are not my libs, and I cannot be responsible for keeping an
> eye on the
> version that get released or the integration into blender whenever there
> is a
> code incompatible update.
>
> Issue is nobody seems to be taking responsibility for the libs, hence they
> lag or
> only get updated cause the new version solves build issues I have. Ideally
> we'd
> assign each and  every one of the 30+ libs we have to a module, and the
> module
> owners request updates to them. They don't have to worry about specific
> build-flags
> for mac/linux/windows platform devs are quicker and better at it however
> if your
> module depends on a external dependency keep an eye on it!
>
> Can dalai organize anything in this department? doesn't have to be my idea
> but we have to do a better/more structured job at managing these deps.
>
> --Ray
>
> On 2020-01-11 8:05 p.m., Stephen Swaney wrote:
> > Following the VFX Platofrm for a year is reasonable.
> > The problem with doing it long-term is they are handicapped by their
> > reliance on Qt, something we thankfully don't suffer from.
> >
> > Upgrading our dependent libs is a good thing (at least in theory!).
> >
> > I seem to recall seeing a bunch of bugs related to Intel TBB on Windows
> > which makes rolling back to U6 from U9 a bit scary.  Although, newer is
> not
> > always better.  Ray would be a better person to comment on this since he
> is
> > in it up to his ears.
> >
> > S.
> >
> > On Fri, Jan 10, 2020 at 1:03 PM Ray Molenkamp <ray at lazydodo.com> wrote:
> >
> >> That's me hence i'm asking if i should update these libs or not :)
> >>
> >> --Ray
> >>
> >> On 2020-01-10 10:54 a.m., Ton Roosendaal wrote:
> >>> Hi,
> >>>
> >>> To my knowledge these differences are minor and won't be a showstopper
> >> for studio pipelines.
> >>> I will leave it to the platform maintainers though :)
> >>>
> >>> -Ton-
> >>> ----------------------------------------------------------------------
> >>> Ton Roosendaal - ton at blender.org - www.blender.org
> >>> Chairman Blender Foundation, Director Blender Institute
> >>> Buikslotermeerplein 161, 1025 ET Amsterdam, the Netherlands
> >>>
> >>>
> >>> On 10/01/2020 18:30, Ray Molenkamp wrote:
> >>>> I took a quick survey, most of the libs are either not applicable to
> us
> >> (QT related stuff) or at the preferred version already
> >>>> however some of them are lagging behind a bit (or a lot in case of
> >> openVDB) and one of them is a little ahead of the VFX platform
> >>>> Behind:
> >>>> OpenEXR    VFX:2.4.x    Blender:2.3.0
> >>>> OpenSubdiv VFX:3.4.x    Blender:3.4.0 RC2
> >>>> OpenVDB    VFX:7.x      Blender:5.1.0
> >>>> Boost      VFX:1.7      Blender:1.68
> >>>>
> >>>> Ahead:
> >>>> Intel TBB  VFX:2019_U6  Blender:2019_U9
> >>>>
> >>>> Is the plan to get at-least the lagging ones up to the VFX versions
> for
> >> 2.83?
> >>>> --Ray
> >>>>
> >>>>
> >>>> On 2020-01-10 10:03 a.m., Ton Roosendaal wrote:
> >>>>
> >>>>> Hi everyone,
> >>>>>
> >>>>> Blender has always been an early adopter of new libraries. We moved
> to
> >> Python 3 ten years ago already. Unfortunately that made Blender
> >> incompatible with the Python 2.7 infrastructure in many studios. But the
> >> industry is catching up! Python 3.7 is now the reference standard.
> >>>>> To give studios enough time and confidence to check out on Blender, I
> >> propose to respect the VFX Platform versions for the entire year of
> 2020.
> >> That implies we will be very conservative with upgrading libraries, for
> >> example Python will stick to 3.7 this year for official releases.
> >>>>> I've checked it with the core team and administrators, and they're OK
> >> - provided this won't hold back essential improvements for our users.
> >>>>> Check the reference platform here:
> >>>>> https://vfxplatform.com/
> >>>>>
> >>>>> Thanks,
> >>>>>
> >>>>> -Ton-
> >>>>>
> ----------------------------------------------------------------------
> >>>>> Ton Roosendaal - ton at blender.org - www.blender.org
> >>>>> Chairman Blender Foundation, Director Blender Institute
> >>>>> Buikslotermeerplein 161, 1025 ET Amsterdam, the Netherlands
> >>>>>
> >>>>>
> >>>>> _______________________________________________
> >>>>> Bf-committers mailing list
> >>>>> Bf-committers at blender.org
> >>>>> https://lists.blender.org/mailman/listinfo/bf-committers
> >>>> _______________________________________________
> >>>> Bf-committers mailing list
> >>>> Bf-committers at blender.org
> >>>> https://lists.blender.org/mailman/listinfo/bf-committers
> >>> _______________________________________________
> >>> Bf-committers mailing list
> >>> Bf-committers at blender.org
> >>> https://lists.blender.org/mailman/listinfo/bf-committers
> >> _______________________________________________
> >> Bf-committers mailing list
> >> Bf-committers at blender.org
> >> https://lists.blender.org/mailman/listinfo/bf-committers
> >>
> > _______________________________________________
> > Bf-committers mailing list
> > Bf-committers at blender.org
> > https://lists.blender.org/mailman/listinfo/bf-committers
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at blender.org
> https://lists.blender.org/mailman/listinfo/bf-committers
>