As promised, I've added just a couple minor fixes since last week, called it a
"release candidate," and tagged as Release-1.5.9RC1.
I'm aiming to tag as Release-1.5.10 (no RC) on Friday, with no changes between
now and then other than solving build breaks and fixing critical bugs.
I've also tagged Release-1.4.16, incorporating the few fixes done lately in the
RB-1.4 tree (release notes below). I'm hoping that this will be the last 1.4
release, because as soon as 1.5 is fully released, everybody should be
switching to it as soon as possible.
Release 1.4.16 (19 Jan 2015 -- compared to 1.4.15)
--------------------------------------------------
* Fix gcc 4.9 warnings.
* Improved error propagation through ImageCache, ImageBuf, and oiiotool.
* TIFF more robust to Exif blocks with corrupted GPS data. #1008
* Support for freetype 2.5.4. #1012
* Better exception safety in Filesystem::exists() and similar functions. #1026
Moving forward, the general rule of thumb is:
master - new development, anything goes
RB-1.5 - stable release, fixes and minor features that don't break APIs/ABIs
RB-1.4 - old release, most critical bug fixes only, and only if requested
RB-1.3 and earlier: deprecated, will not fix.
On Jan 12, 2015, at 11:12 AM, Larry Gritz <[email protected]> wrote:
> Welcome to 2015!
>
> I've created an OpenImageIO "RB-1.5" branch, and tagged its current head as
> "Release-1.5.8beta1".
>
> Now is the time to make sure you can build successfully on your platform of
> choice (and please send patch suggestions for how to fix anything broken), so
> we can be confident of clean builds to have a final release.
>
> Since quite a few places (including my company) tend to work right out of
> master, I'm fairly confident that the current code is solid, so I'm hoping
> for a very short "beta" period (basically, this week), followed by a "release
> candidate", and barring critical bugs, an official release no later than some
> time next week.
>
> If anybody has a patch (or a request for a fix) that will necessitate a
> non-backwards-compatible change to public APIs or linkage, speak up
> IMMEDIATELY, or be resigned for it to be part of the 1.6 development.
>
> I will soon update the versioning of "master" to reflect that it's
> in-progress work on an eventual 1.6, and of course new features may be added
> at any time that break compatibility. Note also that, as discussed before,
> for 1.6 we are going to assume a minimum of gcc 4.8.1 / clang 3.3 / Visual
> Studio 2012. In the coming weeks, we'll try to sort out exactly which new C++
> features we want to encourage in future development. But the upshot is that
> at some point this year, it's likely that if you are still using older
> compiler versions (despite http://www.vfxplatform.com/), you may find
> yourself stuck with OIIO 1.5 until you catch up.
>
>
--
Larry Gritz
[email protected]
_______________________________________________
Oiio-dev mailing list
[email protected]
http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
