Skip to end of banner
Go to start of banner

2021-05-03 Capacity Planning Meeting

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 20 Next »

Date

3-May-2021

Attendees

MembersAttended
Kelly DrakeX
Mike GorrellX
Harry KaplanianX
Holly MistlebauerX
Jakub SkoczenX
Mark VekslerX

Guests: Kyle, Charlotte and Ann-Marie


Discussion items

Item

Presenter

Notes

Approval for R1 2021 Hot Fixes:  Memory leaks as described in

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



Kyle Felker

CIRC-1121 and CIRC-1117 have been approved as hot fixes to R1 2021.
Approval for R1 2021 Hot Fix:  Normalized call number UI error (bug is being created)Charlotte WhittCannot reproduce bug, so skip this.
Approval for R1 2021 Hot Fix: Six JIRAsAnn-Marie Breaux (Deactivated)

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.


Goals/strategies for R2 (Juniper=Bug Squashing) - and beyondMark Veksler

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

Now that Iris will go out May 3rd, should we review
  1. what's currently in scope for Juniper AND
  2. discuss who is working on the Rel Engineering goals? 

I would like to use that info to identify critical tracks (my guess is that Data Import should be one of them) for us to monitor in the weekly folio update meetings.
Kiwi pointing exercise resultsHolly



  • No labels