... and it was immediate updated with Release-2.1.18.1 after discovering that 
it was still reporting itself as 2.1.17 rather than 18.



> On Jul 31, 2020, at 2:18 PM, Larry Gritz <[email protected]> wrote:
> 
> We have tagged Release-2.1.18.0 and moved the "release" marker to that spot. 
> This is the new fully-supported release version of OIIO, and is guaranteed to 
> be backward-compatible in source, API, ABI, and linkage with prior 2.1.x 
> releases. Release notes are below:
> 
> Release 2.1.18 (1 Aug 2020) -- compared to 2.1.17
> -------------------------------------------------
> * Python `ImageBuf.write()` added a variety that takes an open ImageOutput.
>  This is the key to writing multi-subimage files from Python. #2640
> * `oiiotool --eraseattrib` fixed: was not applying to all subimages. #2632
> * RAW: Improve thread safety when more than one thread might be opening
>  different raw files at the same time. #2633
> * unordered_map_concurrent fixed a missing size decrement upon erase(). #2624
> * Fixes to support certain recent pybind11 changes. #2637
> * Fixes to support OpenColorIO v2. #2636
> * Fixes to support more recent fmtlib versions. #2639
> * PNG: document the "png:compressionLevel" output hint. #2642
> * In oiioversion.h, add a `OIIO_MAKE_VERSION` macro that constructs the
>  integer code for a particular major/minor/patch release. #2641
> 

--
Larry Gritz
[email protected]




_______________________________________________
Oiio-dev mailing list
[email protected]
http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org

Reply via email to