build(deps): Raise minimum OpenImageIO version to 2.4 #1722
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
This seem ok to everybody? |
This is just for future-looking OSL 1.13 releases, it won't be backported to the 1.12 release branch. Remember that by the time we release OSL 1.13 as a supported release family, OIIO will also have done its annual release, of 2.5. So our minimum of OIIO 2.4 means that we will be supporting the current release, as well as the prior year's release (and, of course, we always stay compatible with OIIO's trunk as it evolves). So we're really keeping compatibility with 3 major releases, which seems like plenty to juggle. Signed-off-by: Larry Gritz <lg@larrygritz.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is just for future-looking OSL 1.13 releases, it won't be backported to the 1.12 release branch.
Remember that by the time we release OSL 1.13 as a supported release family, OIIO will also have done its annual release, of 2.5. So our minimum of OIIO 2.4 means that we will be supporting the current release, as well as the prior year's release (and, of course, we always stay compatible with OIIO's trunk as it evolves). So we're really keeping compatibility with 3 major releases, which seems like plenty to juggle.
We discussed doing this a few TSC meetings ago, and nobody raised any objections to our raising the OIIO floor to 2.4 for the upcoming OSL 1.13 release. But if anyone is bothered by this, please speak up on this PR.