Bump version, CHANGES is current, rebuild docs
OpenEXR fix misunderstanding: scanline files cannot be written in random order.
Fixes for BUILDSTATIC + Linux

Python bindings require dynamic library that needs different -fPIC
setting than is used when building .a, so don't build Python bindings on
Linux when BUILDSTATIC=1.
Fix OpenEXR brittleness with malformed metadata.
Our particular case was a string called "tiles" -- triggers an exception
inside libIlmImf.
Fixes for standard IlmBase/OpenEXR 2.1 installation
Fix errors in mitchell and gaussian default width. Fixes #835.
Mitchell should be 4, was incorrectly 3. Gaussian should be 3, was 2.
Note that there has always been "sharp-gaussian", which is 2 by design.
The fact that "gaussian" was also 2 is clearly a typo, there's no reason
for us to have intentionally made "gaussian" and "sharp-gaussian" identical.
Add operator< to TypeDesc, also conform the comparison arguments to usual.
Rename string_ref to string_view to match nomenclature of C++17 drafts.
Add round_to_multiple_of_pow2 to fmath
spin_rw_lock: Add more standard "lock/unlock" and "lock_shared/unlock_shared"
as synonyms for read locks and write locks, respectively. This is more in
conforming to recent C++ shared lock nomenclature.
Fix comment.
Add functors for ordering ustrings, helpful for sorted containers
Improve help message for --cut
Allow unordered_map_concurrent caller to specify a custom bin container
Add retrieve(), slightly faster than find when you need a value, not iterator.
Also align bins to cache lines for very slight extra multithread speed.
ustring -- use unordered_map_concurrent, much faster with many threads.
Slightly slower with just 1 thread, break even with 2 threads.
Much faster with >= 4 threads, have seen 25% or more speed gain in benchmarks
involving many threads creating ustrings with high frequency.
Also use cache alignment to eliminate false sharing for the statistics counts.
Our own simplified FindFreetype replaces buggy cmake version.
Finally add a test for oiiotool --text to be sure we don't break it again.
Add ImageBuf::Iterator::rerange resets an iterator's range on the same image
without having to go through the full construction of a new iterator.

Also changed the value I use for uninitialized position, which was
troublingly 0xffffffff (-1, which is not an unreasonable coordinate
value) to 1<<31, which will definitely never be a valid image
coordinate.
Add ParamValueList::find methods.

Similar to what used to be in the implementation of
ImageSpec::find_attribute, but it seems like it's more appropriate to be
right in the PVL.
Fix image_view::AutoStride -- it was unwisely evaluating to -1
Somebody might actually want that as a stride.
Seems safe to use PTRDIFF_MIN, which is impossible to use as a meaningful
stride.