Yes, this year, I have been in discussion with Turnitin's Integrations teams and have learned that they are working on updates to their integrations. While speaking with them, both parties have decided that the LTI implementation of Turnitin in Sakai's Assignments will no longer be required when their new offerings are available in Sakai in the next year or two - Bryan Holladay is working on the replacement implementation for Sakai's Assignments and Content Review, as you mentioned, in SAK-39967. Turnitin has confirmed that they will keep their Legacy API available until the new offerings are available.

We have decided that instead of having Sakai schools switch from using the Legacy API to using the LTI implementation and then switch again to the new offering in a year or two, it will be less disruptive for schools to switch their Turnitin implementation once to the new offering when it is ready.

With this new plan, Western has ceased work on porting our Turnitin LTI implementation of Content Review to Sakai Master, as it will no longer be needed by the Sakai community.

For other Sakai schools using Turnitin in Sakai's Assignments tool, my advice is to continue to use the current Turnitin Legacy API until Turnitin's new Content Review implementation in Assignments is available. Turnitin has informed me that their LTI connection is still available to link to Turnitin as an external tool using BasicLTI (separate of Sakai's Assignments).

I sent similar messaging to the Sakai mailing lists (Core, Dev, User, and Sakai Turnitin) with additional information on May 25, 2018. I've also updated the Content Review page with this status update: https://confluence.sakaiproject.org/display/TII/Home

I feel like this will be incorporated by and no longer done. Please re-open if this isn't the case.

I think we discussed that UWO is working on 10 branch but may not need to contribute that back since others are continuing to use the existing API and the hope is to get it merged into master after UWO completes their local work?

Correction: We'll contribute to 11.x, then 10, and do master last

Western is nearly finished QA'ing our LTI integration against our fork of Sakai 10.3 before our local deployment next week, and then we'll begin contributing to 11.x and master. This is gonna take some strategy as we've done quite a bit of work on this over the past few months. Merging back to Sakai 10 would be the last step, but since Turnitin has pushed their Sakai API cutoff date back, it's a question if there are institutions that would like to use Turnitin that cannot upgrade to 11 in time.