WAIT!!! I just found a problem. Hold on 10 minutes, I'm going to change this tag.
On Jan 8, 2014, at 9:14 AM, Larry Gritz <[email protected]> wrote: > And right on its heels, the next release, mainly to address build breakage > issues on 1.3.10. > > Tagged as Release-1.3.11 : > > Release 1.3.11 (8 Jan 2013 -- compared to 1.3.10) > ------------------------------------------------- > * DPX output: honor the "Software" metadata attribute passed in. > * OpenEXR: fix crashing bug when reading stringvector attributes in the > file. > * Fix build breaks when building against OpenEXR 1.x. > * Fix warnings with Boost Python + gcc 4.8. > > > > On Jan 6, 2014, at 12:09 PM, Larry Gritz <[email protected]> wrote: > >> I've tagged Release-1.3.10. It's a bug-fix release with the following >> release notes: >> >> >> Release 1.3.10 (2 Jan 2013 -- compared to 1.3.9) >> ------------------------------------------------ >> * OpenEXR fix: multi-part EXR (2.0) didn't write the required "name" >> attribute for each part. >> * iconvert: properly handle multi-image files for formats that can't >> append subimages. >> * iv info window should print native file info, not translated >> ImageBuf/ImageCache info. >> * Improved strutil_test now much more comprehensively unit tests >> Strutil. >> * Strutil::split() fixes bug when maxsplit is not the default value. >> * Fix ImageCache::get_pixels() for the chbegin != 0 case, when cache >> and output buffer types were not identical. >> * DPX bug fix -- inappropriate use of "dpx_ImageDescriptor" could make >> invalid DPX files (especially when reading metadata from one DPX >> file, changing the number of channels, then writing out again as a >> DPX file). >> >> >> Release-1.3.10 is now the current recommended stable version for production >> use. >> >> Branch RB-1.3 generally will continue to incorporate fixes and occasional >> safe enhancements, but will not break backwards API or ABI compatibility. >> Presumably it will eventually be tagged with 1.3.{>=11}. >> >> Branch RB-1.2 and older are considered deprecated, and will not be patched >> unless somebody specifically requests a fix to be backported to them. >> >> Branch master is where new development happens, is subject to unannounced >> API or ABI changes, and will eventually become the basis for a 1.4 release. >> >> -- >> Larry Gritz >> [email protected] >> >> >> >> _______________________________________________ >> oiio-announce mailing list >> [email protected] >> http://lists.openimageio.org/listinfo.cgi/oiio-announce-openimageio.org > > -- > Larry Gritz > [email protected] > > > > _______________________________________________ > Oiio-dev mailing list > [email protected] > http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org -- Larry Gritz [email protected] _______________________________________________ Oiio-dev mailing list [email protected] http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
