I was able to successfully upgrade now from Q1 to Q2 with mod-cal and mod-orders RMB updates.

Great - thanks very much,

If sysOps use latest platform-complete or platform-core to run the upgrade they are safe.
The first module in
https://github.com/folio-org/platform-complete/blob/q2-2020/install.json
is mod-orders-storage 11.0.3 that has the RMB fix.
The first module in
https://github.com/folio-org/platform-core/blob/q2-2020/install.json
is mod-calendar 1.9.1 that has the RMB fix.

If the first module fixes the issue all following modules upgrade successfully even if they use old RMB versions.

I've added an upgrade considerations entry to the Goldenrod release notes:
https://folio-org.atlassian.net/wiki/pages/viewpage.action?pageId=5210318#Q22020(Goldenrod)ReleaseNotes(InProgress)-ImportantUpgradeConsiderations

Hi and We're trying to figure out if any additional work is needed for MODORGSTOR-74, MODCONF-54, or MODPERMS-88 or they can just be closed. With regards to 's concern a few comments above - would there be a need to upgrade mod-orders-storage before the other affected apps? If that's required, we definitely need to document in the release notes on the wiki. Plus I'm wondering if that requirement might cause issues for upgrading libraries, especially since MODPERMS is one of the affected apps, and it usually needs to be deployed early in the sequencing (I think). Thank you!

cc:

Closing this ticket.