2021-05-03 Capacity Planning Meeting

CIRC-1121 and permission error as described in CIRC-1117

Cannot reproduce bug, so skip this.

(This was a misunderstanding - so not about call number, normalized BUT Shelving order. The bug ticket UIIN-1499 was addressed on Friday 4/30, and all work completed and tested)

https://folio-org.atlassian.net/secure/Dashboard.jspa?selectPageId=11810

MODDICORE-136 has been approved as a hot fix to R1 2021.

A decision on MODDATAIMP-423 has been postponed due to too many unknowns.  This issue should be a "Spike".

MODDATAIMP-390 has been approved as a hot fix to R1 2021.  Could wait for the 2 hot fix release.

MODINV-400 should be fixed in one of the two hot fix releases, but need dev input as to what is happening and how long it will take to fix.

MODSOURMAN-454 should be fixed in one of the two hot fix releases, but need dev input as to what is happening and how long it will take to fix.

MODDATAIMP-422 should be fixed in one of the two hot fix releases, but need dev input as to what is happening and how long it will take to fix.

We have previously discussed Goals/strategies for R2 (Juniper=Bug Squashing):

• Bug reduction, stability, and sustainability
• Rel Eng: 

• Document dependencies, come up with the design and implementation plan for R3
• Stretch goal: inform the plan with a POC which allows to drop/replace an app with a new version

• Scope: for Juniper

• Limit to 

• Bugs fixes (P1s, P2s, P3s) and performance only
• Production issues resulting from the Iris go-lives (P1s and P2s only)
• If 0 P1/0P2s then can work on roll-over features
• Delivering all features, tests, bugfixes, etc by the deadlines

1. what's currently in scope for Juniper AND
2. discuss who is working on the Rel Engineering goals?