Page Comparison

Jakub Skoczen

• Mid sprint 69
• Platform Q3.1 updates:
  • General platform bugfixes for Q3.1:
    • Image RemovedRMB-432 - fulltext: word splitting and punctuation removal IN PROGRESS  and  
    • Image RemovedRMB-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 RemovedFOLIO-2102 - Spike: timestamp metadata missing from bootstrap data OPEN
  • Image RemovedUXPROD-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 RemovedRMB-395 - support nested sub queries across multiple tables IN PROGRESS  is developed to address two remaining perf test issues:  
        • Image RemovedMODINVSTOR-256 - /instance-storage/instances?query=holdingsRecords.permanentLocationId=abc* does not perform BLOCKED
        • Image RemovedMODINVSTOR-292 - Search instances by item.barcode is slow BLOCKED  
  • Image RemovedUXPROD-1827 - CI-integrated continuous deployment (Q3, FOLIO setup) IN PROGRESS 
    
    • Image RemovedFOLIO-2183 - integrate backend-module pipeline into Jenkins CLOSED
    • Image RemovedFOLIO-2187 - refactor Ansible roles so they can be used on K8s IN PROGRESS
    • Image RemovedFOLIO-2194 - Develop script to clean up expired K8 container instances OPEN
    • Image RemovedFOLIO-2056 - create a pipeline for a front-end module that builds and deploys to K8s cluster OPEN
    • Image RemovedFOLIO-2195 - Implement EFK logging stack on folio-eks-oregon-1 K8 cluster CLOSED
    • Image RemovedFOLIO-2131 - SPIKE: how to deploy containers based on feature branches IN PROGRESS
• Platform Q3.2 work:
  • Image RemovedUXPROD-1815 - support for upgrading schemas without complete reload of data (DB migrations)IN PROGRESS
    • Image RemovedFOLIO-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 RemovedFOLIO-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 RemovedUXPROD-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 RemovedUXPROD-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 RemovedUXPROD-1815 - support for upgrading schemas without complete reload of data (DB migrations)IN PROGRESS
    • Image RemovedFOLIO-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