I have now tagged Release-1.6.7RC1 (with a few minor fixes while beta). This is a release candidate. Assuming no critical errors or important platforms it will not build properly on, I'm expecting to make this an official release early next week, at which point 1.6 will be the preferred release branch and 1.5 will be considered the old release slated for critical bug fixes only.
I have also heard no objections to the plan for allowing the current master (future 1.7) to have a minimum requirement of C++11. Don't worry, I'm not planning to proactively break for old compilers right away, but whenever it naturally comes up that we want to use a C++11 idiom we will do so without feeling it necessary to defensively #ifdef it. > On Dec 2, 2015, at 12:39 AM, Larry Gritz <[email protected]> wrote: > > At long last, I have created an RB-1.6 branch, and tagged its current top as > Release-1.6.6beta. There are a whole lot of important things to pay attention > to: > > My goal is to beta for a couple weeks, then have a release candidate or two, > and before the end of 2015 call it final and set the "release" branch to > point to RB-1.6, at which point 1.6.x will be the official stable production > release. > > I will strive not to break API/ABI/link compatibility in RB-1.6, but there > may still be minor tinkering during the beta period. But absent a change > that's critical to squeeze into 1.6, anything that breaks compatibility or > adds nontrivial risk will go in master only (which henceforth is in-progress > 1.7, though I won't actually diverge and bump the version number until the > first time we have something to commit that can't go in 1.6). > > OIIO has been heavily used in production -- many studios build from master > (or very close to it) for a wide range of production tools -- so I am very > confident about its basic correctness and performance. I know it builds on > OSX with a modern clang, and RedHat-like Linux with gcc 4.2-4.9 (or clang), > in both default C++03 and C++11 (the latter requires you to build with the > option USE_CPP11=1). But if you are on a different platform (especially > Windows, Debian, BSD) or a more bleeding-edge compiler please please do a > test build now, so we can fix any build issues on your platform before the > beta period ends. > > The current plan is that all 1.6.x updates will remain compatible with C++03, > but that post-release, the new master (the in-progress 1.7) will have as a > MINIMUM requirement C++11, gcc 4.8.2 or clang 3.5 or MSVS (whichever MSVS > version is C++11 compliant). If you have a problem with that, i.e. if you > anticipate needing major OIIO features not yet in 1.6 before you are able to > switch to C++11, then speak up now!! Please note that the VFX Platform > standards (http://www.vfxplatform.com/) dictate C++11 baseline for all > 2016-released software for the VFX industry, so you are severely behind if > you can't deal with this. Along those lines, we also anticipate that 1.7 will > assume a minimum Boost of 1.55. > > Happy beta, please test, and I'll try hard to declare this all final by the > end of the month. > -- Larry Gritz [email protected] _______________________________________________ Oiio-dev mailing list [email protected] http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
