Page Comparison

• Mid Sprint 73
• Platform Q3.2 updates (dev):
  • Various security-related issues brought up last week took precedence over other work:
    •  

      Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key OKAPI-763

       solution for 

      Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key FOLIO-2287

    • Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key OKAPI-764

       solution for 

      Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key FOLIO-2286

    • Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key RMB-478

  • Chalmers-related performance and stability issues:

    • Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UICHKIN-111

       all individual backend tickets have been addressed (for list see previous report) besides:

    • • Jira Legacy
        server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODAT-51

      • Jira Legacy
        server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODPERMS-67

      • Jira Legacy
        server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODUSERS-150

      • Problems to be addressed by other teams are still incomplete:

        • Jira Legacy
          server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODSOURCE-76

           

        • Jira Legacy
          server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODNOTIFY-54

      • The ticket to replicate check-in/check-out performance issues on the Perf test env by adding more realistic circulation data is pending: 

        Jira Legacy
        server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key CIRC-466

    • Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UXPROD-1820

      New development work (RMB 27.x related) has been resumed this week:

      • Jira Legacy
        server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODINVSTOR-256

         pending verification

      • Jira Legacy
        server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODINVSTOR-349

         enabler for 

        Jira Legacy
        server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UIIN-564

         is back in development
• Platform Q3.2 updates (devops):
  • Standard release related activities have been completed last week (what remain is ad-hoc hotfix releases) and the team has resumed focus on Continuous Deployment work, namely:

  • Jira Legacy
    server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key FOLIO-2227

     which consists of the following sub-tasks:

    • Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key FOLIO-2275

    • Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key FOLIO-2265

    • Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key FOLIO-2267

    • Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key FOLIO-2268

  • Additionally the following CI problems are being addressed:

    • Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key FOLIO-2060

    • Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key FOLIO-2276

    • Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key FOLIO-2282

    • Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key FOLIO-2237

• Q3.2 (Daisy) release:
  • release pending on a bugfix for 

    Jira Legacy
    server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UIU-1271

     which should be available related today
  • during 

    Jira Legacy
    server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UIU-1271

     another problem has been discovered, 

    Jira Legacy
    server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key STCOR-392

    , will be addressed by a Stripes bugfix release after Q3.2
  • Bugfix release cycle for Q3.1, Q3.2 and preview release for Q4  should be established ASAP. Currently it's not clear for how long we'd like to support Q3.1 (and going forward Q3.2) and release bugfixes. Proposal:
    • end-of-life Q3.1 asap – e.g mid-October (depends on Chalmers upgrade plans)
    • continue publishing bugfix releases (critical defects only) for Q3.2 until and including Jan 2020
  • release spreadsheet: https://docs.google.com/spreadsheets/d/1DKV8rf3kD7QAz57etqA-C2FqHHLZmRVmMZFobvDszn8/edit#gid=0

Cate Boerema (Deactivated)

• Chalmers is live!
• Bugs and enhancement requests are beginning to come in: 

  Jira Legacy
  server System JIRA jqlQuery filter=11808 count true serverId 01505d01-b853-3c2e-90f1-ee9b165564fc

• Have created first pass at release notes accessible from here: Cross Release Statistics
• Q3 needs to be wrapped up in JIRA.  There are still ~10 open UXPRODs

Jakub Skoczen

• Started Sprint 73
• Platform Q3.2 updates (dev):

  • Jira Legacy
    server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UXPROD-1820

     RMB 27.x related:

    • Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key RMB-468

       enabler for 

      Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODINVSTOR-256

       has been completed and awaits roll-out this sprint 

    • Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODINVSTOR-349

       enabler for 

      Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UIIN-564

       requires functionality that was missing from 

      Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key RMB-385

      and has been BLOCKED and postponed to the next sprint to allow the Platform team to focus on performance issues this sprint
  • Chalmers-related performance and stability issues:

    • Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UICHKIN-111

       has been broken down into a set of analysis tasks last sprint: 

      • Jira Legacy
        server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key CIRC-448

      • Jira Legacy
        server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key CIRC-452

      • Jira Legacy
        server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key CIRC-453

      • Jira Legacy
        server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key CIRC-464

    • The analysis uncovered various performance problems in individual storage and low-level BL APIs. Some of the problems are addressed directly by the Platform team while others are being addressed by the teams responsible for individual modules.

      • Jira Legacy
        server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODUSERS-150

      • Jira Legacy
        server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODPERMS-66

      • Jira Legacy
        server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODAT-49

      • Jira Legacy
        server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODAT-51

      • Jira Legacy
        server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODCAL-50

         (this problem has surfaced during check-out, not check-in, see UICHKOUT-541)
      • Problems to be addressed by individual teams:

        • Jira Legacy
          server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODSOURCE-76

           

        • Jira Legacy
          server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODNOTIFY-54

    • Additionally the Platform team will work to reproduce perf issues locally (so far the analysis used only the logfiles, limiting how thorough it can be) 

      • Jira Legacy
        server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key CIRC-466

    • Stability problems being addressed:

      • Jira Legacy
        server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODPERMS-64

• Platform Q3.2 updates (devops):
  • Standard release related activities have been completed last week (what remain is ad-hoc hotfix releases) and the team has resumed focus on Continuous Deployment work, namely:

  • Jira Legacy
    server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key FOLIO-2227

     which consists of the following sub-tasks:

    • Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key FOLIO-2275

    • Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key FOLIO-2265

    • Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key FOLIO-2267

    • Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key FOLIO-2268

  • Additionally the following CI problems are being addressed:

    • Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key FOLIO-2060

    • Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key FOLIO-2276

    • Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key FOLIO-2237

• Q3.2 (Daisy) release:
  • Module release deadline: 11th September, midnight GMT
  • Bugfix release deadline: 25th September, midnight GMT
  • release spreadsheet: https://docs.google.com/spreadsheets/d/1DKV8rf3kD7QAz57etqA-C2FqHHLZmRVmMZFobvDszn8/edit#gid=0

Cate Boerema (Deactivated)

• Loan policy testing in BugFest was blocked until today due to 

  Jira Legacy
  server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key CIRC-461

   It is now blocked due to insufficient bandwidth on my part.  I'll do my best
• Currently working to keep Core Functional's backlog ahead of development.  This means reviewing and clarifying Sean's Loan policy features and helping Charlotte and Laura with the Call number features 
• Very concerned about lack of dev-ready backlog across the board: https://folio-org.atlassian.net/secure/RapidBoard.jspa?rapidView=130
• One more hotfix coming soon for Chalmers to address 

  Jira Legacy
  server System JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key CHAL-29

   and 

  Jira Legacy
  server System JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key CHAL-30

• Only one more 3.2 bug still open for Core: Functional but it's likely not to make it at this point.  This is not a must-have for Chalmers: 

  Jira Legacy
  server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UIIN-725

Jakub Skoczen

• Mid Sprint 71
• Platform Q3.2 updates (dev):

  • Jira Legacy
    server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UXPROD-1820

     RMB 27 released, ongoing work in particular modules to roll out new functionality:

    • Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key RMB-385

       enabler for 

      Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODINVSTOR-349

       which in turn addresses 

      Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UIIN-564

    • Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key RMB-468

       enabler for resolution of following perf issue: 

      Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODINVSTOR-256

       
  • Remaining Chalmers-related issues:
    •  brought up today by Cate, to be discussed at Platform's standup

    • Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UICHKIN-111

       has been broken down into following optimization tickets:

      • Jira Legacy
        server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key CIRC-448

      • Jira Legacy
        server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key CIRC-452

      • Jira Legacy
        server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key CIRC-453

• Platform Q3.2 updates (devops):
  • Focus on Daisy release activities

    • Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key FOLIO-2262

       

    • Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key FOLIO-2252

    • Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key FOLIO-2259

    • Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key FOLIO-2258

    • Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key FOLIO-2257

  • Jira Legacy
    server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UXPROD-1827

    
    

    • Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key FOLIO-2011

       will be showcased at the PO meeting on Wednesday
    • Remaining FOLIO-1827 blockers:

    • Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key FOLIO-2252

       

    • Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key FOLIO-2056

      , which is blocked on:

      • Jira Legacy
        server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key FOLIO-2249

    • Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key FOLIO-2227

       to be addressed in sprint 72
• Q3.2 (Daisy) release:
  • Module release deadline: 11th September, midnight GMT
  • Bugfix release deadline: 25th September, midnight GMT
  • release spreadsheet: https://docs.google.com/spreadsheets/d/1DKV8rf3kD7QAz57etqA-C2FqHHLZmRVmMZFobvDszn8/edit#gid=0

Cate Boerema (Deactivated) 

Development:

• Have hotfixed several bugs for Chalmers: 

  Jira Legacy
  server System JIRA jqlQuery labels in (hotfixed) AND status = closed ORDER BY key ASC count true serverId 01505d01-b853-3c2e-90f1-ee9b165564fc

• Still working through several important issues:

  • Jira Legacy
    server System JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key CIRC-440

     - Development complete.  Testing in folio-snapshot now (looks good so far!)

  • Jira Legacy
    server System JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UICHKIN-111

     - Backend optimizations being worked by Core Platform.  With Zak and Marc back at work, Core Functional will look at the proposal for frontend optimizations in grooming today (UICHKIN-112).  RA SIG has discussed performance requirements and check in is needed to take less than one second for barcode scanners.  Should be 1/3 of a second for RFID scanners.  See performance requirements page: /wiki/spaces/DQA/pages/2658550

  • Jira Legacy
    server System JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UIIN-687

     - Work Ryan did to 

    Jira Legacy
    server System JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key STCOR-388

     may have helped but didn't solve the problem.  He continues to investigate.  This turns out to be easier to reproduce than initially thought (it doesn't take hours to build this latency - just a bit of activity across inventory, requests and users).  New, clarified repro steps should help with locating the problem
• Some new circ issues are popping up as Chalmers continues to migrate data.  These may require additional hotfixes:

  • Jira Legacy
    server System JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key CHAL-29

  • Jira Legacy
    server System JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key CHAL-30

Testing:

• Request test cases have been fleshed out in TestRail (steps and expected behavior in all tests)
• I've assigned myself all the loan policy test cases, as they need fleshing out - CIRC-440 revealed that we have not done sufficient testing in this area
• Recent performance issues and bugs like 

  Jira Legacy
  server System JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key CHAL-29

   and 

  Jira Legacy
  server System JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key CHAL-30

   make me wonder if our performance and load testing is sufficient.

Planning:

• RA SIG invited Cap planning group to discuss non-MVP features.  There are many features implementing institutions feel are deal-breakers for go live (see 2019-9-16 Resource Access Meeting Notes).  General agreement was that we need to get requirements ready so that, when/if development resources become available, they are ready to pick up.    

Jakub Skoczen

• Sprint 71
• Platform Q3.2 updates (dev):

  • Jira Legacy
    server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UXPROD-1820

     RMB 27, more releases last sprint, new features completed and more in progress

    • Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key RMB-385

    • Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key RMB-457

    • Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key RMB-468

       potential solution for the following perf issues:
  • Chalmers-related issues:

    • Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key CIRC-447

       solution for 

      Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UIREQ-335

    • Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key OKAPI-759

    • Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key OKAPI-760

    • Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODUSERS-147

       brought up today by Cate, to be discussed at Platform's standup

    • Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UICHKIN-111

       perf-related, no longer assigned to anyone since beginning of the week, discussed with Cate today and it will be brought up at the Platform stand-up (backend portion of the problem may be addressed)
• Platform Q3.2 updates (devops):

  • Jira Legacy
    server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UXPROD-1827

    
    

    • Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key FOLIO-2011

       has been completed, test PR available at https://github.com/folio-org/platform-core/pull/382
    • Remaining FOLIO-1827 blockers: 

    • Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key FOLIO-2056

      , which is blocked on:

      • Jira Legacy
        server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key FOLIO-2249

    • Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key FOLIO-2227

• Q3.2 (Daisy) release:
  • Module release deadline: 11th September, midnight GMT
  • Bugfix release deadline: 25th September, midnight GMT
  • release spreadsheet: https://docs.google.com/spreadsheets/d/1DKV8rf3kD7QAz57etqA-C2FqHHLZmRVmMZFobvDszn8/edit#gid=0

Cate Boerema (Deactivated)

• Module release deadline for Q3.2 (Daisy) is end of day today
• Many PRs for circulation (mod-circulation) came in about a week before the deadline and Marc Johnson asked for priorities, as it didn't seem they would all be able to be reviewed in time.  POs prioritized features affecting Chalmers.

Jakub Skoczen

• Sprint 71
• Platform Q3.2 updates (dev):

  • Jira Legacy
    server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UXPROD-1820

     RMB 27 initial release performed last week, includes clean-up and bugfixes for RMB26 series, new functionality:

    • Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key RMB-459

       
      which (once RMB27 is rolled out to storage modules, see

      Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODUSERS-142

       and

      Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODINVSTOR-342

      ) will address 

      Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key FOLIO-2102

    • Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key RMB-452

    • Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key RMB-451

    • Many other fixes, full list here: 

      Jira Legacy
      server System JIRA jqlQuery project = RMB AND fixVersion = 27.0.0 count true serverId 01505d01-b853-3c2e-90f1-ee9b165564fc

      
      
    • tickets that are in the pipeline for the next RMB27.x releases:

      • Jira Legacy
        server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key RMB-454

        
        RMB26 regression, not critical for existing functionality 

      • Jira Legacy
        server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key RMB-385

      • Jira Legacy
        server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key RMB-457

        
        helper utility to address remaining performance problems: 

        Jira Legacy
        server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODINVSTOR-256

         and 

        Jira Legacy
        server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODINVSTOR-336

• Platform Q3.2 updates (devops):

  • Jira Legacy
    server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UXPROD-1827

    
    

    • Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key FOLIO-2011

      
      is finally in the sprint, the plan is to rollout PR preview functionality to "platform-core" this sprint. It will work on top of the new FOLIO K8s-based CI cluster but initially will include several limitations, e.g no ability to user "feature branch builds". This ability will be developed in the coming weeks and the architecture for it has been agreed last week (see 

      Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key FOLIO-2227

      )
    • Remaining FOLIO-2011 blockers: 

    • Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key FOLIO-2194

    • Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key FOLIO-2056

    • Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key FOLIO-2217

  • Jira Legacy
    server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UXPROD-1815

    • Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key FOLIO-2169

• Scaling FOLIO development process:

  • Jira Legacy
    server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key FOLIO-2214

  • Jira Legacy
    server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key FOLIO-2207

  • Jira Legacy
    server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key FOLIO-2208

• Q3/Q4 platform features in DRAFT (requirements and design):

  • Jira Legacy
    server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UXPROD-1928

  • Jira Legacy
    server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UXPROD-1826

Jakub Skoczen

• Sprint 70
• Platform Q3.2 updates:
  • General platform bugfixes for Q3.2:

    • Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key FOLIO-2102

       Spike: timestamp metadata missing from bootstrap data (spillover)
  • Image AddedUXPROD-1818  CLOSEDRMB 26 release features and core module rollout (performance, array search and cross-table search)
    • released RMB 26.4.0, includes performance fixes for slow item.barcode search (

    • Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODINVSTOR-292

    • Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key RMB-411

       

    • Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key RMB-432

    • completed large new functionality 

      Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key RMB-395

       which will help address remaining performance issues (filtering by location and status)
  • Image AddedUXPROD-1827 - CI-integrated continuous deployment (Q3, FOLIO setup) IN PROGRESS 

    • Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key FOLIO-2187

    • Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key FOLIO-2194

    • Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key FOLIO-2056

• Platform Q3.2 work:
  • Image AddedUXPROD-1815 - support for upgrading schemas without complete reload of data (DB migrations)IN PROGRESS
    • Image AddedFOLIO-2169 - SPIKE investigate schema migrations in platform-core storage modules IN PROGRESS
      • PoC has been executed and the following document is availalbe: https://docs.google.com/document/d/1z6rgZK6EVERzRsvTnTKrCHeE5odaNoSJZqVyipuaEFM/edit?pli=1#
      • Taras prepared a step-by-step guideline document for adding migrations to RMB-based modules, outstanding PR
      • Pu migration requirement for schema changes in the DoD update slides for the Sprint Review
• Q3.1 Release Management:
  • Q3.1 module bugfix release deadline was August 8th, midnight GMT 
  • The “Modules and version” release planning spreadsheet for Q3.1: https://docs.google.com/spreadsheets/d/14zoV755B1kh5_j2CTzYAmHo1_N46RGh5-B4lyG6Qht8/edit#gid=0 
• Scaling FOLIO development process:
  • "FOLIO Tech Design and Code Review process and roles" document: https://docs.google.com/document/d/10cTOkUBpi7myIBQfrvdLGihLE1Wes3rRxFgDZs-Is64/edit#
  • Finalized PR review guidelines and initial CODEOWNERS groups are ready. Next steps planned for sprint 70:
    • task to publish the PR review checklists on dev.folio.org in the current sprint
    • task to publish CODEOWNERS files in mod-inventory/-storage, mod-circulation/-storage is in the current sprint

Jakub Skoczen

• Mid sprint 69
• Platform Q3.1 updates:
  • General platform bugfixes for Q3.1:
    • Image AddedRMB-432 - fulltext: word splitting and punctuation removal IN PROGRESS  and  
    • Image AddedRMB-438 - contributor search returns no results when name contains "-" IN PROGRESS , which block many UI issues, serious but not critical for Q3.1, related to searching terms that include punctuation like apostrophes and hyphens. 
    • Image AddedFOLIO-2102 - Spike: timestamp metadata missing from bootstrap data OPEN
  • Image AddedUXPROD-1818 - RMB 26 release features and core module rollout (performance, array search and cross-table search) IN PROGRESS
    
    • released RMB 26.2.4 (MODINVSTOR-319) and rolled it out to mod-inv-storage (to be released today), RMB 26.2.3 (CIRCSTORE-138) rolled out to mod-circulation-storage (released) and RMB 26.2.2 rolled out to mod-users (released) 
    • Continued focus on performance testing and tuning:
      • Overall perf results look very good (here)
      • Image AddedRMB-395 - support nested sub queries across multiple tables IN PROGRESS  is developed to address two remaining perf test issues:  
        • Image AddedMODINVSTOR-256 - /instance-storage/instances?query=holdingsRecords.permanentLocationId=abc* does not perform BLOCKED
        • Image AddedMODINVSTOR-292 - Search instances by item.barcode is slow BLOCKED  
  • Image AddedUXPROD-1827 - CI-integrated continuous deployment (Q3, FOLIO setup) IN PROGRESS 
    
    • Image AddedFOLIO-2183 - integrate backend-module pipeline into Jenkins CLOSED
    • Image AddedFOLIO-2187 - refactor Ansible roles so they can be used on K8s IN PROGRESS
    • Image AddedFOLIO-2194 - Develop script to clean up expired K8 container instances OPEN
    • Image AddedFOLIO-2056 - create a pipeline for a front-end module that builds and deploys to K8s cluster OPEN
    • Image AddedFOLIO-2195 - Implement EFK logging stack on folio-eks-oregon-1 K8 cluster CLOSED
    • Image AddedFOLIO-2131 - SPIKE: how to deploy containers based on feature branches IN PROGRESS
• Platform Q3.2 work:
  • Image AddedUXPROD-1815 - support for upgrading schemas without complete reload of data (DB migrations)IN PROGRESS
    • Image AddedFOLIO-2169 - SPIKE investigate schema migrations in platform-core storage modules IN PROGRESS
      • PoC has been executed and the following document is availalbe: https://docs.google.com/document/d/1z6rgZK6EVERzRsvTnTKrCHeE5odaNoSJZqVyipuaEFM/edit?pli=1#
      • Next step (Taras) prepare a step-by-step guideline document for adding migrations to RMB-based modules
      • Next step: add migration requirement for schema changes to the DoDs 
• Q3.2 Release Management:

  • the integration tests have been updated to pass on the Q3.1 release and a release tag q3.1-2019 has been created

    • Image AddedFOLIO-2192 - Integrate Q3.1 module releases into platform-core and platform-complete CLOSED
  • mod-login-saml bugfix release 1.2.2 has been released by the Platform team, this module needs maintainers for Q3.2 and Q4.
  • Q3.1 module bugfix release deadline is August 8th, midnight GMT 
  • The “Modules and version” release planning spreadsheet for Q3.1: https://docs.google.com/spreadsheets/d/14zoV755B1kh5_j2CTzYAmHo1_N46RGh5-B4lyG6Qht8/edit#gid=0 
• Scaling FOLIO development process:
  • "FOLIO Tech Design and Code Review process and roles" document: https://docs.google.com/document/d/10cTOkUBpi7myIBQfrvdLGihLE1Wes3rRxFgDZs-Is64/edit#
  • Finalized PR review guidelines and initial CODEOWNERS groups are ready. Next steps planned for sprint 70:
    • publish the PR review checklists on dev.folio.org and create a template for PRs that links to it
    • publish CODEOWNERS files in mod-inventory/-storage, mod-circulation/-storage
    • propose a process for bringing up technical designs for comments on the #tech-leads channel

Cate Boerema (Deactivated)

• Only one must-fix q3.1 bug remains open and it's in review
• Most bugs discovered during bugfest were not deemed must-fix for 3.1
• Otherwise teams are just plugging along with Q3 development

Cate Boerema (Deactivated)

• Module release deadline for the Q3.1 release was last Wednesday
  • It was close, but we managed to close all bugs and must-fix stories in time (see dashboard).  There is one open bug for UNAM - I will follow up with Holly on that.
  • There is some spillover on 

    Jira Legacy
    server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UXPROD-1653

    which has proved a very complex feature to develop
    • Must fix for Q3.2: 

      Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key CIRCSTORE-142

        (I would caution Chalmers against using this feature until these bugs have been addressed)
    • Nice to have: 

      Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UIREQ-294

       
  • General UI performance issues (

    Jira Legacy
    server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key STCON-85

    ) were significantly improved but not completely alleviated. Per Michal, "there is nothing else we can do about this. I feel like we did everything possible given our current architecture (stripes-connect, redux-form). In order to improve it we would have to restructure things significantly (replace redux-form and switch to GraphQL)."  Status on that initiative?
• Cap planning and MVP
  • Cap plan will be updated this evening and so POs are being asked to do any last rankings (there are still some who haven't done the assignment - see unranked features)
  • Cap planning team needs to assemble proposal for PC by Aug 8th
  • Discussion tomorrow with cap plan group, Charlotte and select MM SMEs on how we can best evaluate what Inventory features are must have for MVP
  • Jump in functional features targeted for Q3 (see stats on right - we are now targeting 140 functional issues up from 134 two weeks ago) is, in part, due to POs breaking down their features so they can be better ranked.  After evaluation, some may be removed from Q3

Jakub Skoczen

• Started sprint 69
• Platform Q3.1 updates:
  • General platform bugfixes for Q3.1:

    • Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODINVSTOR-319

       regression when new style array search is mixed with a filter that requires a DB view (e.g location search), resolved. Issues like this will be addressed wholesale when RMB-395 is completed.

    • Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key RMB-432

       and 

      Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key RMB-438

      , which block many UI issues, serious but not critical for Q3.1, related to searching terms that include punctuation like apostrophes and hyphens. While RMB-438 would address also 

      Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UIREQ-295

       /

      Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key CIRCSTORE-138

      we decided to expedite a fix for this issue through 

      Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key RMB-439

    • Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key FOLIO-2102

  • Image AddedUXPROD-1818 - RMB 26 release features and core module rollout (performance, array search and cross-table search) IN PROGRESS
    
    • released RMB 26.2.4 (MODINVSTOR-319) and rolled it out to mod-inv-storage (to be released today), RMB 26.2.3 (CIRCSTORE-138) rolled out to mod-circulation-storage (released) and RMB 26.2.2 rolled out to mod-users (released) 
    • Continued focus on performance testing and tuning:
      • Overall perf results look very good (here) and the new early warning system for missing indexes is extremely useful for catching potential perf issues before they manifest on a system with large data sets, all warnings seen for Q3.1 have been addressed through 

        Jira Legacy
        server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key FOLIO-2176

      • Jira Legacy
        server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key RMB-395

         is developed to address two remaining perf test issues: 

        Jira Legacy
        server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODINVSTOR-256

         and 

        Jira Legacy
        server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODINVSTOR-292

         
  • Image AddedUXPROD-1827 - CI-integrated continuous deployment (Q3, FOLIO setup) IN PROGRESS 
    

    • Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key FOLIO-2183

    • Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key FOLIO-2187

    • Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key FOLIO-2194

    • Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key FOLIO-2056

    • Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key FOLIO-2195

    • Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key FOLIO-2131

• Platform Q3.2 work:
  • Image AddedUXPROD-1815 - support for upgrading schemas without complete reload of data (DB migrations)IN PROGRESS
    • Image AddedFOLIO-2169 - SPIKE investigate schema migrations in platform-core storage modules IN PROGRESS roughly specced out the requirements and scope, Taras has begun work on the SPIKE in Sprint 68
• Q3.2 Release Management:
  • Q3.1 initial module release deadline (July 24th) is passed us and all modules have seen releases
  • the release environment has been updated to include new modules: https://folio-release.aws.indexdata.com/
  • there are integration test failures that we would like to address before finalizing (creating a branch) for Q3.1: 

    Jira Legacy
    server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key FOLIO-2192

  • Q3.1 module bugfix release deadline is August 8th, midnight GMT 
  • The “Modules and version” release planning spreadsheet for Q3.1: https://docs.google.com/spreadsheets/d/14zoV755B1kh5_j2CTzYAmHo1_N46RGh5-B4lyG6Qht8/edit#gid=0 
• Scaling FOLIO development process:
  • "FOLIO Tech Design and Code Review process and roles" document is in initial draft: https://docs.google.com/document/d/10cTOkUBpi7myIBQfrvdLGihLE1Wes3rRxFgDZs-Is64/edit#
  • Updates to the PR review guidelines and initial CODEOWNERS groups are ready, next meeting on Wednesday to finalize the list and groups

Jakub Skoczen

• Started sprint 68
• Platform Q3.1 updates:
  • General platform bugfixes critical for Q3.1:

    • Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODAT-47

       which addresses the problem reported in 

      Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key CIRC-379

       a Pull Request is ready but requires refactoring

  • Jira Legacy
    server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UXPROD-1818

    
    
    • Most UI bugs resolved (confirmed) or reassigned to front-end developers (Core: functional), one remaining:

      • Jira Legacy
        server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key RMB-432

    • Continued focus on performance testing and tuning:
      FOLIO-2143 uncovered some performance issues which have been addressed in Sprint 67

      • Jira Legacy
        server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key RMB-429

      • Jira Legacy
        server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key RMB-417

    • and some bugs that are being addressed this sprint:

      • Jira Legacy
        server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key RMB-430

    • Overall perf results look very good and the new WARNING system for missing indexes is extremely useful for providing new performance optimizations
    • New feature development for:

      • Jira Legacy
        server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key RMB-395

         likely shipped in RMB 27 to address the remaining perf issues (item.barcode and holdings.location search)

  • Jira Legacy
    server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UXPROD-1827

    
    
    • AWS/EKS cluster set up tasks completed (including ingress and Ansible roles)

    • Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key FOLIO-2055

       to be completed this week
    • Added several SPIKEs this sprint for remaining issues:

      • Jira Legacy
        server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key FOLIO-2131

      • Jira Legacy
        server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key FOLIO-2130

      • Jira Legacy
        server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key FOLIO-2089

• Platform Q3.2 work already begun:

  • Jira Legacy
    server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UXPROD-1815

    • Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key FOLIO-2169

       roughly specced out the requirements and scope, Taras has begun work on the SPIKE in Sprint 68
• Q3.2 Release Management:
  • The “Modules and version” release planning spreadsheet for Q3.1 is ready: https://docs.google.com/spreadsheets/d/14zoV755B1kh5_j2CTzYAmHo1_N46RGh5-B4lyG6Qht8/edit#gid=0
  • As usual, lead maintainers will update the “Release Version” and “Interface Required/Provided” columns. If there is a bugfix release for Q3.1 (released past the module release deadline) they will also update the “Bugfix release version” column.
  • Q3.1 module release deadline is July 24th, midnight GMT 
  •  Q3.1 module bugfix release deadline is August 8th, midnight GMT 
• Scaling FOLIO development process:
  • "FOLIO Tech Design and Code Review process and roles" document is in initial draft: https://docs.google.com/document/d/10cTOkUBpi7myIBQfrvdLGihLE1Wes3rRxFgDZs-Is64/edit#
  • Tech-leads kick off meeting (to discuss the document and plan future meeting cadence) is scheduled for Wednesday, 8:00 EST

Cate Boerema (Deactivated)

• Q3.1 must-fix bugs and features are moving along.  Key updates:
  • Bugs:
    • Critical performance bug is making large parts of FOLIO nearly unusable (Users, Inventory etc): 

      Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key STCON-85

        Michal has a fix in code review, but it's complex and his first PR had to be reworked
    • Stripes issue causing many search bugs in Inventory is In review: 

      Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key STSMACOM-229

        This fix should significantly improve searching experience in Inventory
    • I just noticed this bug on the dashboard (it wasn't assigned a development team).  We need to get this assigned to a team with backend capacity: 

      Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key CIRC-390

  • Features:
    • Moving requests from one item to another - All major stories have been completed but a couple have been re-opened due to failed scenarios.  Still tracking for completion by next Wed (module release deadline)
    • Title level and item level requests - Magda and team working through last issues now that they have integration environment working
    • SIP2 - Magda and team working on PIN verification
• Beyond Q3.1 for Core Functional
  • Inventory notes feature completed
  • Lots of new controlled vocabularies added for instance record
  • Charlotte readying additional stories for development
  • Also prioritizing wrapping up wiring in of loan policy settings around hold requests 
• Permissions
  • Have been testing user app permissions and there are issues (lots of permissions give access to more than they should while others are missing things which result in errors when working)
    • Have updated the Users app permission tab and discussed with Emma, Holly and Patty
    • Need to create a user story for cleanup
    • In the meantime, it's really important that we find out what permission sets Chalmers intends to use and make sure they work (Anton is looking into this)

Cate Boerema (Deactivated)

• Q2 Clover release live as of yesterday!
• Release notes and statistics will be available by end of week
• Next big release is Q3 Daisy
  • Dashboard: https://folio-org.atlassian.net/secure/Dashboard.jspa?selectPageId=10627
  • Team plans are still being worked out, but each team has enough to get started
  • Q3 plans may evolve over the course of the quarter as we get the results of the SIG re-ranking exercise and with the capacity planning group's proposed plan for summer 2020
• Next interim release is Q3.1
  • This is the release Chalmers will go live on
  • Module release deadline is July 24th, release is August 12
  • Anton has created a dashboard for bugs and we have extended to include the must-have features for the release, as well.  May also include the must-have stories.  
• Capacity planning group meeting every couple of days with goal to have a plan for how the release proposal will be made prior to the stakeholder meeting
• SIGs are working with POs to re-rank features.  Meetings I have attended so far have been really productive.
• Core functional team:
  • Focus on the must-have bugs and features for Q3.1:
    • SIP2
    • Title level requests
    • Move requests from one item to another
  • Also working on Inventory cleanup:
    • Search bugs and enhancements - Charlotte is coordinating joint SME/Dev discussions on search to help identify the highest impact fixes.
    • Completing incomplete features in instance, holding and item
    • Niels Erik will be available on Core team full-time in July (apart from planned vacation)

Jakub Skoczen

• Starting sprint 67 (first sprint of Q3)!
• Release Management
  • Clover (Q2.2) is out!
    • reference release environment at https://folio-clover.aws.indexdata.com/
    • platform-core (all modules) release branch: https://github.com/folio-org/platform-complete/tree/q2.2-2019
    • folio-install (single-server and K8s/EKS installation documentation): https://github.com/folio-org/folio-install/tree/q2-2019
• Platform Q2.2 summary:
  • FOLIO-2119 Preview capability for PRs (Q2, development)
  • FOLIO-2118 CI-integrated continuous deployment (Q2, cluster setup)
  • FOLIO-2117 Kubernetes integration (Q2, containerization)
  • FOLIO-1936 Q2: secure folio-snapshot and folio-testing Okapi installations
  • FOLIO-1934 RMB 25 release (performance, refactoring)
• Platform Q3.1 plans:
  • UXPROD-1827 CI-integrated continuous deployment (Q3, FOLIO setup)
  • UXPROD-1817 Preview capability for PRs (Q3, rollout)
  • UXPROD-1818 RMB 26 release features and core module rollout (performance, array search and cross-table search)
  • UXPROD-1823 Kubernetes integration (Q3, Okapi features)