Page Comparison

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://issues.folio.org/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)