Date   

Re: 1.1.0 Release

Richard Shaw <hobbe...@...>
 

Ok, I spoke too soon, this doesn't look like a missing package problem:

! Package babel Error: You haven't specified a language option.

See the babel package documentation for explanation.

Thanks,
Richard


Re: 1.1.0 Release

Richard Shaw <hobbe...@...>
 

I'm getting it figured out... It's missing texlive packages but I don't want to install EVERYTHING because there's tons of packages, so I'm having to find what's missing one at a time and keep trying to build.

Thanks,
Richard


Re: 1.1.0 Release

Richard Shaw <hobbe...@...>
 

On Fri, Jan 12, 2018 at 6:48 AM, Sean Cooper <se...@...> wrote:
What issues are you having with the documentation? 

In my previous email I pasted the output from building the pdf documentation. For some reason pdflatex is getting to an interactive prompt which is of course bad when trying to build a package :) 

Thanks,
Richard


Re: 1.1.0 Release

Sean Cooper <se...@...>
 

What issues are you having with the documentation? 

On Jan 12, 2018 12:44 PM, "Richard Shaw" <hobbe...@...> wrote:
On Fri, Jan 12, 2018 at 4:57 AM, Sean Cooper <se...@...> wrote:
Richard, have you tested Patrick's PR for the GCC fixes? I'm looking to release today and don't want to slot in unnecessary commits to the release, they have already been merged to master so will show up in OCIO 1.1.1 down the road.

Let me know you thoughts

Yes, this is with the PR already being applied as a patch, I appear to only be having issues with building the documentation. I can disable that but I would hate to release a new package without the documentation when the previous one had it...

Is it just the extended documentation that I would be missing?

Thanks,
Richard 

--
You received this message because you are subscribed to the Google Groups "OpenColorIO Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ocio-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: 1.1.0 Release

Richard Shaw <hobbe...@...>
 

On Fri, Jan 12, 2018 at 4:57 AM, Sean Cooper <se...@...> wrote:
Richard, have you tested Patrick's PR for the GCC fixes? I'm looking to release today and don't want to slot in unnecessary commits to the release, they have already been merged to master so will show up in OCIO 1.1.1 down the road.

Let me know you thoughts

Yes, this is with the PR already being applied as a patch, I appear to only be having issues with building the documentation. I can disable that but I would hate to release a new package without the documentation when the previous one had it...

Is it just the extended documentation that I would be missing?

Thanks,
Richard 


Re: 1.1.0 Release

Sean Cooper <se...@...>
 

Richard, have you tested Patrick's PR for the GCC fixes? I'm looking to release today and don't want to slot in unnecessary commits to the release, they have already been merged to master so will show up in OCIO 1.1.1 down the road.

Let me know you thoughts

On Fri, Jan 12, 2018 at 12:28 AM, Richard Shaw <hobbe...@...> wrote:
Ok, so I "fixed" it by adding --install-dir to all the python external projects but now I run into this:

[ 61%] Building pdf doc
cd /home/build/rpmbuild/OpenColorIO/BUILD/OpenColorIO-RB-1.1/build/docs/build-latex && /usr/bin/pdflatex OpenColorIO.tex
This is pdfTeX, Version 3.14159265-2.6-1.40.17 (TeX Live 2016) (preloaded format=pdflatex)
 restricted \write18 enabled.
entering extended mode
(./OpenColorIO.tex
LaTeX2e <2016/03/31>
Babel <3.9r> and hyphenation patterns for 3 language(s) loaded.
(./sphinxmanual.cls
Document Class: sphinxmanual 2009/06/02 Document class (Sphinx manual)
(/usr/share/texlive/texmf-dist/tex/latex/base/report.cls
Document Class: report 2014/09/29 v1.4h Standard LaTeX document class
(/usr/share/texlive/texmf-dist/tex/latex/base/size10.clo
kpathsea: Running mktextfm cmr10
/usr/share/texlive/texmf-dist/web2c/mktexnam: Could not map source abbreviation  for cmr10.
/usr/share/texlive/texmf-dist/web2c/mktexnam: Need to update ?
mktextfm: Running mf-nowin -progname=mf \mode:=ljfour; mag:=1; nonstopmode; input cmr10
This is METAFONT, Version 2.7182818 (TeX Live 2016) (preloaded base=mf)


kpathsea: Running mktexmf cmr10
! I can't find file `cmr10'.
<*> ...e:=ljfour; mag:=1; nonstopmode; input cmr10
                                                  
Please type another input file name
! Emergency stop.
<*> ...e:=ljfour; mag:=1; nonstopmode; input cmr10
                                                  
Transcript written on mfput.log.
grep: cmr10.log: No such file or directory
mktextfm: `mf-nowin -progname=mf \mode:=ljfour; mag:=1; nonstopmode; input cmr10' failed to make cmr10.tfm.
kpathsea: Appending font creation commands to missfont.log.

! Font OT1/cmr/m/n/10=cmr10 at 10.0pt not loadable: Metric (TFM) file not found
.
<to be read again> 
                   relax 
l.54 \normalsize
                

And it pauses there waiting for input, which is bad of course since it should be non-interactive.

Thanks,
Richard

--
You received this message because you are subscribed to the Google Groups "OpenColorIO Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ocio-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: 1.1.0 Release

Richard Shaw <hobbe...@...>
 

Ok, so I "fixed" it by adding --install-dir to all the python external projects but now I run into this:

[ 61%] Building pdf doc
cd /home/build/rpmbuild/OpenColorIO/BUILD/OpenColorIO-RB-1.1/build/docs/build-latex && /usr/bin/pdflatex OpenColorIO.tex
This is pdfTeX, Version 3.14159265-2.6-1.40.17 (TeX Live 2016) (preloaded format=pdflatex)
 restricted \write18 enabled.
entering extended mode
(./OpenColorIO.tex
LaTeX2e <2016/03/31>
Babel <3.9r> and hyphenation patterns for 3 language(s) loaded.
(./sphinxmanual.cls
Document Class: sphinxmanual 2009/06/02 Document class (Sphinx manual)
(/usr/share/texlive/texmf-dist/tex/latex/base/report.cls
Document Class: report 2014/09/29 v1.4h Standard LaTeX document class
(/usr/share/texlive/texmf-dist/tex/latex/base/size10.clo
kpathsea: Running mktextfm cmr10
/usr/share/texlive/texmf-dist/web2c/mktexnam: Could not map source abbreviation  for cmr10.
/usr/share/texlive/texmf-dist/web2c/mktexnam: Need to update ?
mktextfm: Running mf-nowin -progname=mf \mode:=ljfour; mag:=1; nonstopmode; input cmr10
This is METAFONT, Version 2.7182818 (TeX Live 2016) (preloaded base=mf)


kpathsea: Running mktexmf cmr10
! I can't find file `cmr10'.
<*> ...e:=ljfour; mag:=1; nonstopmode; input cmr10
                                                  
Please type another input file name
! Emergency stop.
<*> ...e:=ljfour; mag:=1; nonstopmode; input cmr10
                                                  
Transcript written on mfput.log.
grep: cmr10.log: No such file or directory
mktextfm: `mf-nowin -progname=mf \mode:=ljfour; mag:=1; nonstopmode; input cmr10' failed to make cmr10.tfm.
kpathsea: Appending font creation commands to missfont.log.

! Font OT1/cmr/m/n/10=cmr10 at 10.0pt not loadable: Metric (TFM) file not found
.
<to be read again> 
                   relax 
l.54 \normalsize
                

And it pauses there waiting for input, which is bad of course since it should be non-interactive.

Thanks,
Richard


Re: 1.1.0 Release

Richard Shaw <hobbe...@...>
 

On Wed, Jan 10, 2018 at 7:23 PM, Patrick Hodoul <patric...@...> wrote:

If you have some time you could do a pull request :) to help the community...

Yeah, I've thought about it. I actually added most of the USE_EXTERNAL... stuff when I first got OCIO in Fedora but I have far fewer free cycles these days.

Thanks,
Richard


Re: 1.1.0 Release

Patrick Hodoul <patric...@...>
 


If you have some time you could do a pull request :) to help the community...


On Wednesday, January 10, 2018 at 4:40:41 PM UTC-5, Richard wrote:
I think that's because ubuntu uses debian's scheme instead of /usr/lib{,64} like RPM based distros. Either way, there's still the question about why the system installed setuptools isn't used...

Thanks,
Richard


Re: 1.1.0 Release

Richard Shaw <hobbe...@...>
 

I think that's because ubuntu uses debian's scheme instead of /usr/lib{,64} like RPM based distros. Either way, there's still the question about why the system installed setuptools isn't used...

Thanks,
Richard


Re: 1.1.0 Release

Patrick Hodoul <patric...@...>
 

double-checked using the ubuntu 16 & gcc 5.4.0 docker image and setuptools is working fine.

On Tuesday, January 9, 2018 at 10:23:15 AM UTC-5, Richard wrote:
Ok, next error, setuptools is built thinking it needs /usr/lib but installs to /usr/lib64 (as it should) and then it gets confused. 

Side question: Why do we have to build a bundled setuptools instead of using what's available, at least on linux?

Thanks,
Richard

creating build/lib/setuptools
copying setuptools/dist.py -> build/lib/setuptools
copying setuptools/script template (dev).py -> build/lib/setuptools
copying setuptools/depends.py -> build/lib/setuptools
copying setuptools/package_index.py -> build/lib/setuptools
copying setuptools/archive_util.py -> build/lib/setuptools
copying setuptools/compat.py -> build/lib/setuptools
copying setuptools/ssl_support.py -> build/lib/setuptools
copying setuptools/py27compat.py -> build/lib/setuptools
copying setuptools/sandbox.py -> build/lib/setuptools
copying setuptools/py26compat.py -> build/lib/setuptools
copying setuptools/version.py -> build/lib/setuptools
copying setuptools/py24compat.py -> build/lib/setuptools
copying setuptools/__init__.py -> build/lib/setuptools
copying setuptools/site-patch.py -> build/lib/setuptools
copying setuptools/extension.py -> build/lib/setuptools
copying setuptools/script template.py -> build/lib/setuptools
creating build/lib/_markerlib

...

[ 31%] Performing install step for 'setuptools'
cd /home/build/rpmbuild/OpenColorIO/BUILD/OpenColorIO-RB-1.1/build/src/core_tests && /usr/lib64/ccache/c++  -DOCIO_SOURCE_DIR=/home/build/rpmbuild/OpenColorIO/BUILD/OpenColorIO-RB-1.1 -DOCIO_UNIT_TEST -DOpenColorIO_STATIC -DUSE_SSE -I/home/build/rpmbuild/OpenColorIO/BUILD/OpenColorIO-RB-1.1/export -I/home/build/rpmbuild/OpenColorIO/BUILD/OpenColorIO-RB-1.1/build/export -I/home/build/rpmbuild/OpenColorIO/BUILD/OpenColorIO-RB-1.1/ext/oiio/src/include -I/home/build/rpmbuild/OpenColorIO/BUILD/OpenColorIO-RB-1.1/build/ext/dist/include  -O2 -g -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -m64 -mtune=generic -Wall -Wextra -Wshadow -Wconversion -Wcast-qual -Wformat=2 -msse2 -O2 -g -DNDEBUG   -DTIXML_USE_STL   -fPIC -fvisibility=hidden -o CMakeFiles/ocio_core_tests.dir/__/core/GpuShaderUtils.cpp.o -c /home/build/rpmbuild/OpenColorIO/BUILD/OpenColorIO-RB-1.1/src/core/GpuShaderUtils.cpp
cd /home/build/rpmbuild/OpenColorIO/BUILD/OpenColorIO-RB-1.1/build/docs/setuptools-prefix/src/setuptools && PYTHONPATH=/home/build/rpmbuild/OpenColorIO/BUILD/OpenColorIO-RB-1.1/build/ext/dist/lib64/python2.7/site-packages: python setup.py install --prefix=/home/build/rpmbuild/OpenColorIO/BUILD/OpenColorIO-RB-1.1/build/ext/dist

...

TEST FAILED: /home/build/rpmbuild/OpenColorIO/BUILD/OpenColorIO-RB-1.1/build/ext/dist/lib/python2.7/site-packages/ does NOT support .pth files
error: bad install directory or PYTHONPATH

You are attempting to install a package to a directory that is not
on PYTHONPATH and which Python does not read ".pth" files from.  The
installation directory you specified (via --install-dir, --prefix, or
the distutils default setting) was:

    /home/build/rpmbuild/OpenColorIO/BUILD/OpenColorIO-RB-1.1/build/ext/dist/lib/python2.7/site-packages/

and your PYTHONPATH environment variable currently contains:

    '/home/build/rpmbuild/OpenColorIO/BUILD/OpenColorIO-RB-1.1/build/ext/dist/lib64/python2.7/site-packages:'

Here are some of your options for correcting the problem:

* You can choose a different installation directory, i.e., one that is
  on PYTHONPATH or supports .pth files

* You can add the installation directory to the PYTHONPATH environment
  variable.  (It must then also be on PYTHONPATH whenever you run
  Python and want to use the package(s) you are installing.)

* You can set up the installation directory to support ".pth" files by
  using one of the approaches described here:


Please make the appropriate changes for your system and try again.


Re: 1.1.0 Release

Richard Shaw <hobbe...@...>
 

Ok, next error, setuptools is built thinking it needs /usr/lib but installs to /usr/lib64 (as it should) and then it gets confused. 

Side question: Why do we have to build a bundled setuptools instead of using what's available, at least on linux?

Thanks,
Richard

creating build/lib/setuptools
copying setuptools/dist.py -> build/lib/setuptools
copying setuptools/script template (dev).py -> build/lib/setuptools
copying setuptools/depends.py -> build/lib/setuptools
copying setuptools/package_index.py -> build/lib/setuptools
copying setuptools/archive_util.py -> build/lib/setuptools
copying setuptools/compat.py -> build/lib/setuptools
copying setuptools/ssl_support.py -> build/lib/setuptools
copying setuptools/py27compat.py -> build/lib/setuptools
copying setuptools/sandbox.py -> build/lib/setuptools
copying setuptools/py26compat.py -> build/lib/setuptools
copying setuptools/version.py -> build/lib/setuptools
copying setuptools/py24compat.py -> build/lib/setuptools
copying setuptools/__init__.py -> build/lib/setuptools
copying setuptools/site-patch.py -> build/lib/setuptools
copying setuptools/extension.py -> build/lib/setuptools
copying setuptools/script template.py -> build/lib/setuptools
creating build/lib/_markerlib

...

[ 31%] Performing install step for 'setuptools'
cd /home/build/rpmbuild/OpenColorIO/BUILD/OpenColorIO-RB-1.1/build/src/core_tests && /usr/lib64/ccache/c++  -DOCIO_SOURCE_DIR=/home/build/rpmbuild/OpenColorIO/BUILD/OpenColorIO-RB-1.1 -DOCIO_UNIT_TEST -DOpenColorIO_STATIC -DUSE_SSE -I/home/build/rpmbuild/OpenColorIO/BUILD/OpenColorIO-RB-1.1/export -I/home/build/rpmbuild/OpenColorIO/BUILD/OpenColorIO-RB-1.1/build/export -I/home/build/rpmbuild/OpenColorIO/BUILD/OpenColorIO-RB-1.1/ext/oiio/src/include -I/home/build/rpmbuild/OpenColorIO/BUILD/OpenColorIO-RB-1.1/build/ext/dist/include  -O2 -g -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -m64 -mtune=generic -Wall -Wextra -Wshadow -Wconversion -Wcast-qual -Wformat=2 -msse2 -O2 -g -DNDEBUG   -DTIXML_USE_STL   -fPIC -fvisibility=hidden -o CMakeFiles/ocio_core_tests.dir/__/core/GpuShaderUtils.cpp.o -c /home/build/rpmbuild/OpenColorIO/BUILD/OpenColorIO-RB-1.1/src/core/GpuShaderUtils.cpp
cd /home/build/rpmbuild/OpenColorIO/BUILD/OpenColorIO-RB-1.1/build/docs/setuptools-prefix/src/setuptools && PYTHONPATH=/home/build/rpmbuild/OpenColorIO/BUILD/OpenColorIO-RB-1.1/build/ext/dist/lib64/python2.7/site-packages: python setup.py install --prefix=/home/build/rpmbuild/OpenColorIO/BUILD/OpenColorIO-RB-1.1/build/ext/dist

...

TEST FAILED: /home/build/rpmbuild/OpenColorIO/BUILD/OpenColorIO-RB-1.1/build/ext/dist/lib/python2.7/site-packages/ does NOT support .pth files
error: bad install directory or PYTHONPATH

You are attempting to install a package to a directory that is not
on PYTHONPATH and which Python does not read ".pth" files from.  The
installation directory you specified (via --install-dir, --prefix, or
the distutils default setting) was:

    /home/build/rpmbuild/OpenColorIO/BUILD/OpenColorIO-RB-1.1/build/ext/dist/lib/python2.7/site-packages/

and your PYTHONPATH environment variable currently contains:

    '/home/build/rpmbuild/OpenColorIO/BUILD/OpenColorIO-RB-1.1/build/ext/dist/lib64/python2.7/site-packages:'

Here are some of your options for correcting the problem:

* You can choose a different installation directory, i.e., one that is
  on PYTHONPATH or supports .pth files

* You can add the installation directory to the PYTHONPATH environment
  variable.  (It must then also be on PYTHONPATH whenever you run
  Python and want to use the package(s) you are installing.)

* You can set up the installation directory to support ".pth" files by
  using one of the approaches described here:


Please make the appropriate changes for your system and try again.


Re: 1.1.0 Release

Patrick Hodoul <patric...@...>
 

Please have a look to PR #498 to have the standalone fix (for gcc 5.4.0)


On Sunday, January 7, 2018 at 9:37:50 PM UTC-5, Patrick Hodoul wrote:
Using newer gcc version (i.e. 7.2.1), you are facing new warnings.

Please have a look to PR 488 where most of your problems should have been fixed:

Patrick.

On Sunday, January 7, 2018 at 9:29:37 PM UTC-5, Richard wrote:
Ok, so I changed to yaml-cpp 0.5.x (was still using 0.3.x) and got past cmake, now:

/home/build/rpmbuild/OpenColorIO/BUILD/OpenColorIO-RB-1.1/src/core/Lut1DOp.cpp:192:14: error: 'void OpenColorIO::v1::{anonymous}::Lut1D_Nearest(float*, long int, const OpenColorIO::v1::Lut1D&)' defined but not used [-Werror=unused-function]
         void Lut1D_Nearest(float* rgbaBuffer, long numPixels, const Lut1D & lut)
              ^~~~~~~~~~~~~
cc1plus: all warnings being treated as errors


Thanks,
Richard


Re: 1.1.0 Release

Patrick Hodoul <patric...@...>
 

Using newer gcc version (i.e. 7.2.1), you are facing new warnings.

Please have a look to PR 488 where most of your problems should have been fixed:
https://github.com/imageworks/OpenColorIO/pull/488/commits/598f11d995a73d950ab85abeef1f6c2d1a15a6d9

Patrick.


On Sunday, January 7, 2018 at 9:29:37 PM UTC-5, Richard wrote:
Ok, so I changed to yaml-cpp 0.5.x (was still using 0.3.x) and got past cmake, now:

/home/build/rpmbuild/OpenColorIO/BUILD/OpenColorIO-RB-1.1/src/core/Lut1DOp.cpp:192:14: error: 'void OpenColorIO::v1::{anonymous}::Lut1D_Nearest(float*, long int, const OpenColorIO::v1::Lut1D&)' defined but not used [-Werror=unused-function]
         void Lut1D_Nearest(float* rgbaBuffer, long numPixels, const Lut1D & lut)
              ^~~~~~~~~~~~~
cc1plus: all warnings being treated as errors


Thanks,
Richard


Re: 1.1.0 Release

Richard Shaw <hobbe...@...>
 

Ok, so I changed to yaml-cpp 0.5.x (was still using 0.3.x) and got past cmake, now:

/home/build/rpmbuild/OpenColorIO/BUILD/OpenColorIO-RB-1.1/src/core/Lut1DOp.cpp:192:14: error: 'void OpenColorIO::v1::{anonymous}::Lut1D_Nearest(float*, long int, const OpenColorIO::v1::Lut1D&)' defined but not used [-Werror=unused-function]
         void Lut1D_Nearest(float* rgbaBuffer, long numPixels, const Lut1D & lut)
              ^~~~~~~~~~~~~
cc1plus: all warnings being treated as errors


Thanks,
Richard


Re: 1.1.0 Release

Richard Shaw <hobbe...@...>
 

Trying to do a test build on Fedora Rawhide but I'm getting an error:

+ /usr/bin/cmake -DCMAKE_C_FLAGS_RELEASE:STRING=-DNDEBUG -DCMAKE_CXX_FLAGS_RELEASE:STRING=-DNDEBUG -DCMAKE_Fortran_FLAGS_RELEASE:STRING=-DNDEBUG -DCMAKE_VERBOSE_MAKEFILE:BOOL=ON -DCMAKE_INSTALL_PREFIX:PATH=/usr -DINCLUDE_INSTALL_DIR:PATH=/usr/include -DLIB_INSTALL_DIR:PATH=/usr/lib64 -DSYSCONF_INSTALL_DIR:PATH=/etc -DSHARE_INSTALL_PREFIX:PATH=/usr/share -DLIB_SUFFIX=64 -DBUILD_SHARED_LIBS:BOOL=ON -DOCIO_BUILD_STATIC=OFF -DOCIO_BUILD_DOCS=ON -DOCIO_BUILD_TESTS=ON -DOCIO_PYGLUE_SONAME=OFF -DUSE_EXTERNAL_YAML=TRUE -DUSE_EXTERNAL_TINYXML=TRUE -DUSE_EXTERNAL_LCMS=TRUE ../
-- The C compiler identification is GNU 7.2.1
-- The CXX compiler identification is GNU 7.2.1
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Setting Build Type to: RelWithDebInfo
-- Setting Namespace to: OpenColorIO
-- Exec prefix not specified, defaulting to /usr
-- Use Boost Ptr: OFF
-- Setting python bin to: python
Python library: /usr/lib64/python2.7/config/libpython2.7.so
-- Setting EXTDIST_BINPATH: /builddir/build/BUILD/OpenColorIO-RB-1.1/build/ext/dist/bin
-- Setting EXTDIST_PYTHONPATH: /builddir/build/BUILD/OpenColorIO-RB-1.1/build/ext/dist/lib64/python2.7/site-packages
-- Found TinyXML: /usr/lib64/libtinyxml.so  
-- TinyXML version: 2.6.2
-- External TinyXML will be used.
-- Found PkgConfig: /usr/bin/pkg-config (found version "1.4.0") 
CMake Error at /usr/share/cmake/Modules/FindPkgConfig.cmake:415 (message):
  A required package was not found
Call Stack (most recent call first):
  /usr/share/cmake/Modules/FindPkgConfig.cmake:593 (_pkg_check_modules_internal)
  CMakeLists.txt:255 (pkg_check_modules)
-- Configuring incomplete, errors occurred!

Am I missing something? I can't see what's actually wrong...

Thanks,
Richard


1.1.0 Release

Sean Cooper <se...@...>
 

Hello all,

With the help of our lovely contributors, we have just set up the 1.1.0 release branch. This is currently regarded as a Release Candidate since the official 1.1.0 tag has not been assigned yet. We are looking to the community to take a look at this release candidate and provide feedback before the version is officially locked off.

We will be looking to have input before the following Friday (Jan 12 2018). Pending feedback, we will look to lock off the version after this date. All input and opinions are welcomed and appreciated.

Thanks!
SC


Re: OCIO 1.0.10

Sean Cooper <se...@...>
 

Happy New Year everyone!

After some time we finally have some good news. With the help of our lovely contributors over many years, we have just set up the Release Candidate branch for OCIO 1.1.0 here.

Some notes to carry over from the various Slack channel conversations. Between Larry, Patrick and myself we have decided to adopt the OIIO method of maintaining release branches for a given Major+Minor release version. This will allow for continued maintenance of the given release without holding back active development on Master.

Why 1.1.0 instead of 1.0.10? After a bit of deliberation, it seemed more appropriate to assign this a Minor version for a few reasons. First and foremost, its been almost 5 years since the last release and a good amount of changes have accumulated over that time. Additionally, there are backward compatible API changes which require a Minor version change based on SemVer 2.0. Lastly, it allows for a clean beginning to the release branch structure.

I will create another post specific to the 1.1.0 Release Candidate, so please carry your comments and concerns to that thread.

Thanks everyone,
SC


On Wednesday, 26 April 2017 18:31:50 UTC+1, Sean Cooper wrote:
Hello all,

With a little bit of movement on the OCIO repo working towards addressing the most egregious image-quality-effecting bugs, we need to look to locking off to a 1.0.10 to help our users, and product partners.

If you haven't been watching, I invite you to take a look at the OCIO repo, and point out other image quality *bugs* that you deem a requirement for the next minor version. Prior to my involvement there have been a number of commits to master since 1.0.9, and I think it's beneficial to put a stake in the ground as a firm mark of rejuvenation. We can proceed from there.

If you haven't joined in the side Slack conversation where more day-to-day conversation has been centered, please reply below or message me personally I am more than happy to invite you. Or if you have a strong opinion against the "closed-door" conversation, I am open ears.

Thoughts, and opinions welcomed, thanks!
Sean


Re: Slack invite

Espen Nordahl <espen....@...>
 

I'd love to join too.

On Mon, Dec 18, 2017 at 9:13 AM, Simon Björk <bjork...@...> wrote:
I'd like to join as well, thanks



-------------------------------
Simon Björk
Compositor/TD


2017-12-16 16:39 GMT+01:00 Chris Offner <chriso...@...>:
May I also request an invite?
chriso...@...

Thank you! :)

--
You received this message because you are subscribed to the Google Groups "OpenColorIO Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ocio-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "OpenColorIO Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ocio-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Slack invite

Simon Björk <bjork...@...>
 

I'd like to join as well, thanks



-------------------------------
Simon Björk
Compositor/TD

+46 (0)70-2859503

2017-12-16 16:39 GMT+01:00 Chris Offner <chriso...@...>:

May I also request an invite?
chriso...@...

Thank you! :)

--
You received this message because you are subscribed to the Google Groups "OpenColorIO Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ocio-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

501 - 520 of 2154