At this point I'm thinking that this is simply part of the in-development OIIO
1.5 / OSL 1.6. Even after these are officially branched and marked as stable
releases, the older branches (OIIO 1.4 and OSL 1.5) will continue to be
maintained until everybody has switched to the new ones, just as we do for
every major release.
So far, changes to the public APIs are actually very minor and restricted to
TextureSystem. Many/most OIIO-using applications will not have any source
compatibility break at all. (And the TextureSystem changes are truly small --
the biggest incompatibility is that we moved a couple fields out of TextureOpt
and pass those explicitly as parameters to the TS routines that need them.)
The only change from standard operating procedure for us is that usually I try
to make it so that a given release of OSL will work with both the current, and
at least one pervious major release, of OIIO. But this time, when OSL users
upgrade to 1.6, they will be forced to simultaneously upgrade to OIIO 1.5.
Also, if anybody is working directly from the master branches, they will need
to update both packages simultaneously.
-- lg
On Sep 11, 2014, at 6:23 AM, Richard Shaw <[email protected]> wrote:
> With this big of a change (both in performance and API changes), are you
> planning a major version bump?
>
> I'm thinking 1.X may need to be supported for a while until everyone ports
> over and that would make a clear distinction.
>
--
Larry Gritz
[email protected]
_______________________________________________
Oiio-dev mailing list
[email protected]
http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
