CMCL-809: Backports for 2.6.12 #401
Merged
Conversation
This file contains hidden or 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
gaborkb
changed the title
gaborkb
requested review from
AntoineCharton,
JWalker0007,
glabute and
mjmvisser
JWalker0007
approved these changes
Feb 7, 2022
glabute
approved these changes
Feb 14, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
[Delete any line or section that does not apply]
Purpose of this PR
Backports:
https://jira.unity3d.com/browse/CMCL-757 -> #385
https://jira.unity3d.com/browse/CMCL-779 -> #394 and #397
https://jira.unity3d.com/browse/CMCL-783 -> #398
https://jira.unity3d.com/browse/CMCL-622
JIRA:
https://jira.unity3d.com/browse/CMCL-809
Testing status
[Explanation of what’s tested, how tested and existing or new automation tests. Can include manual testing by self and/or QA. Specify test plans. Rarely acceptable to have no testing.]
Documentation status
[Overview of how documentation is affected by this change. If there is no effect on documentation, explain why. Otherwise, state which sections are changed and why.]
Technical risk
Comments to reviewers
Package version