Skip to content

Bump ORA2 version - #38

Merged
jul merged 1 commit into
openfun:fun/release-4.8from
open-craft:bdero/ora2-improvements
Jul 21, 2017
Merged

Bump ORA2 version#38
jul merged 1 commit into
openfun:fun/release-4.8from
open-craft:bdero/ora2-improvements

Conversation

@bdero

@bdero bdero commented Jun 30, 2017

Copy link
Copy Markdown

@bdero
bdero force-pushed the bdero/ora2-improvements branch from 0de3429 to e3f61d6 Compare July 7, 2017 22:54
@bdero

bdero commented Jul 13, 2017

Copy link
Copy Markdown
Author

CC @jul - this is the ORA2 version bump to include the LaTeX fixes

@jul

jul commented Jul 20, 2017

Copy link
Copy Markdown

Sorry to interact so late. Does this includes the multi latex preview?

@jul

jul commented Jul 20, 2017

Copy link
Copy Markdown

PS job appreciated. Currently on staging and giving all satisfaction so far to our concerned users.
Keep up the good work.

@bdero

bdero commented Jul 20, 2017

Copy link
Copy Markdown
Author

Does this includes the multi latex preview?

@jul Yup! It's includes the preview across all fields accepting LaTeX entry along with the fix for the LaTeX option in the studio ORA2 settings.

Thanks for taking a look!

@jul
jul merged commit 40f7a62 into openfun:fun/release-4.8 Jul 21, 2017
@bdero
bdero deleted the bdero/ora2-improvements branch July 22, 2017 19:41
@jul

jul commented Jul 26, 2017

Copy link
Copy Markdown

Hello deployed the bump ORA2 latex instead of my version.

Result: there is a conflict of version between ora2 latex multiple
preview and openedx platform on the dependency of path.py with our current version (7.2 vs 8.2.1)

testing fast that edx-plaftorm can be upgraded to 8.2.1 without harm.

@bdero

bdero commented Jul 27, 2017

Copy link
Copy Markdown
Author

@jul Ah, I actually ran into that same issue when I was testing it against a FUN box, but I neglected to include it. Sorry about that! The solution was indeed changing the required version in edx-platform to match ORA2. I then smoke tested the FUN box and was unable to find broken functionality as a result of the upgrade.

@jul

jul commented Jul 29, 2017

Copy link
Copy Markdown

No worry, it was easy to diagnose, fix and stage once again.
I just put a comment in case someone tripped on the same problem and needed the information.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants