Skip to end of banner
Go to start of banner

Q4 2019 Overall Status Update (History)

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 6 Current »

This page contains historical data from the Overall Status Update table on the FOLIO Q4 2019 (Edelweiss) Weekly Status Report

Report Date

Overall Status Update

Q1 Feature Count on Report Date



FunctionalNFR
2019-11-26

Jakub Skoczen

  • Mid-sprint 77
  • Platform Dev updates:
    • In support of Q4 functionals and defects: 
    • Performance-related issues:
      • RMB-506 - Getting issue details... STATUS  to address various search performance issues, including  MODINVSTOR-256 - Getting issue details... STATUS
      • OKAPI-770 - Getting issue details... STATUS  to address various perf issues, specifically in authn/z subsystem  MODAT-51 - Getting issue details... STATUS
    • MODINVSTOR-353 - Getting issue details... STATUS  completed
    • MODINVSTOR-349 - Getting issue details... STATUS  completed
  • Platform DevOps updates:
    • FOLIO-2227 - Getting issue details... STATUS  PR previews builds are being tested by the Platform DevOps, only one task remains open and it's been partially completed:
      • FOLIO-2268 - Getting issue details... STATUS  remaining work is related to automatically assigning "version" number to preview artifacts.
    • FOLIO-2336 - Getting issue details... STATUS
    • Additionally the following CI problems are being addressed:
      • FOLIO-2315 - Getting issue details... STATUS
      • FOLIO-2218 - Getting issue details... STATUS  related to scaling issues caused by the increased CI/CD requirement
  • Q4 release:

Getting issues...

Getting issues...

2019-11-19

Jakub Skoczen

  • Started sprint 77
  • Platform Dev updates:
    • In support of Q4 functionals and defects: 
    • Performance-related issues:
      • RMB-506 - Getting issue details... STATUS  to address various search performance issues, including  MODINVSTOR-256 - Getting issue details... STATUS
      • OKAPI-770 - Getting issue details... STATUS  to address various perf issues, specifically in authn/z subsystem  MODAT-51 - Getting issue details... STATUS
    • MODINVSTOR-353 - Getting issue details... STATUS  completed
    • MODINVSTOR-349 - Getting issue details... STATUS  completed
  • Platform DevOps updates:
    • FOLIO-2227 - Getting issue details... STATUS  PR previews builds are being tested by the Platform DevOps, only one task remains open and it's been partially completed:
      • FOLIO-2268 - Getting issue details... STATUS  remaining work is related to automatically assigning "version" number to preview artifacts
    • Additionally the following CI problems are being addressed:
      • FOLIO-2315 - Getting issue details... STATUS
      • FOLIO-2218 - Getting issue details... STATUS  related to scaling issues caused by the increased CI/CD requirement
  • Q4 release:
    •  December 4th is the module release deadline

Cate Boerema (Deactivated)

  • Started last sprint of Q4 development
  • Prioritizing wrapping up development on in progress features and priority bug fixes

  • There will be significant spillover (52 issues currently - see table on Q4 2019 Dashboard)

  • In addition to features that will spill over in their entirety, many In progress features will have to be "split" meaning there will be partial carry-over
  • For Core Functional, the following features: will need to be split:
  • Many (most?) features currently "In progress" are likely to need to be split. 
    • In some cases, a good thin thread has been implemented in Q4 and what is left is lower priority and/or small in scope
    • In other cases, a sizeable amount of priority development will need to be split and carried over.
    • Often the remaining development can be completed in the Q4 development period (just too late to make the actual release)
  • The cap planning group is:
    • Evaluating the items that have been tagged by POs as spillover to see which are the highest priority for the 2020 cohort (including Chalmers).  Holly is following up with POs on features that don't have high implementer rankings to better understand their priority.  These usually have explanations e.g.  they represent thin thread workarounds for other features the implementers really need.
    • Gathering info on what the development capacity will be in Q1

Getting issues...

Getting issues...

2019-11-12

Cate Boerema (Deactivated)

  • Second week of second to last development sprint
  • Core functional:
    • Still struggling with  MODINVSTOR-357 - Getting issue details... STATUS .  This feature ( UXPROD-1626 - Getting issue details... STATUS ) has taken all quarter and was estimated at 3 days FE/3 days BE
    • Finally got first story for  UXPROD-2114 - Getting issue details... STATUS  into Code Review and picked up the next one
    • UI developers are working through many Inventory search and filter enhancements, wrapping up Reorder request queue feature and fixing priority bugs (also struggling with integration tests)
  • Overall, currently we have 47 features that have been tagged as likely spillover from Q4 (see dashboard: https://issues.folio.org/secure/Dashboard.jspa?selectPageId=10801)
    • Cap planning team beginning to look at what's there and the capacity for Q1 so we can plan
  • Chalmers continues to uncover issues with operational impact such as:
    • CIRC-543 - Getting issue details... STATUS CHAL-145 - Getting issue details... STATUS  will be hotfixed when ready
    •  needs to be fixed for Q4
      • This issue results from the fact that barcode data isn't synched between Users and Requests
      • We have the same problem with items and requests and are waiting for pub-sub for a complete resolution to this issue
      • In the meantime, we can fix the linking issue with a simple change to how filtering works

Getting issues...

Getting issues...

2019-11-05

Jakub Skoczen

  • Started sprint 75
  • Platform Q3.2 updates (dev):
    • Performance-related issues:
      • Ongoing optimisation work in the authn/z subsystem  MODAT-51 - Getting issue details... STATUS , specifically: 
      • FOLIO-2296 - Getting issue details... STATUS  to help investigate perf problems going forward
      • Pending perf problems to be addressed by other teams: 
      • Other perf issues:
      • RMB-497 - Getting issue details... STATUS  to allow for estimating hitcount and address perf issues like  MODINVSTOR-256 - Getting issue details... STATUS
    • UXPROD-1820 - Getting issue details... STATUS New development work (RMB 28.x related):
      • MODINVSTOR-349 - Getting issue details... STATUS  has been completed (in PR) to allow the Functional team to complete  UIIN-564 - Getting issue details... STATUS
      • RMB-499 - Getting issue details... STATUS  to allow addressing  UIIN-647 - Getting issue details... STATUS
    • Batch import APIs for Inventory:
  • Platform Q3.2 updates (devops):
    • FOLIO-2227 - Getting issue details... STATUS  pending completion on the following tasks:
    • Additionally the following CI problems are being addressed:
      • FOLIO-2315 - Getting issue details... STATUS
      • FOLIO-2218 - Getting issue details... STATUS  related to scaling issues caused by the increased CI/CD requirement
  • Q3.2 (Daisy) release:
    •  Hotfix release issues: (label ^q3.2-2019-hotfix^):
    • Getting issues...

Cate Boerema (Deactivated)

  • Started sprint 76 on Monday - 2 sprints left until module release deadline!
    • Some Core Functional features have been slow-going this quarter because they are things we haven't done before (e.g.  MODINVSTOR-348 - Getting issue details... STATUS ,  UXPROD-1626 - Getting issue details... STATUS  (which had to be implemented differently than the effective location) and  UXPROD-1626 - Getting issue details... STATUS )
    • The team feels we are close to getting being over the hump, at which time development should accelerate
    • Core Functional folks had a good meeting last week with Jakub to discuss plans for Inventory search and filter and we have a clear plan for some long-awaited features such as:
      • UXPROD-1685 - Getting issue details... STATUS  - Now assigned to Core Platform for Q4
      • UIIN-724 - Getting issue details... STATUS  - Which will allow searching by CQL with plans to later implement  UXPROD-1941 - Getting issue details... STATUS  to improve user experience with query validation and potentially reduce performance and stability issues due to bad inputs.  I see this feature is currently marked Q4 2019 for Core Platform.  Is that right?
    • Two disruptive requests bugs were fixed and pushed to Chalmers as a hotfix this week:
      • CIRC-516 - Getting issue details... STATUS
      • UICHKOUT-553 - Getting issue details... STATUS
      • The number of mysterious circulation issues being reported by Chalmers has virtually stopped
    • It looks like there will be more spillover features this quarter than we have seen in the past and the PO have gathered their thoughts on why that may be.  Issues include team turnover and vacations, dependencies between features, underestimated features and late requirements.
    • POs and Anton discussed the desire to capture bug reports from broader community, as implementers are beginning to test in earnest.  Currently thinking about setting up a special project for this purpose.  More conversations are needed and we've submitted as a topic for Wolfcon.

Getting issues...

Getting issues...

2019-10-22

Jakub Skoczen

  • Started sprint 75
  • Platform Q3.2 updates (dev):
    • Security-related:
    • Performance-related issues:
      • UICHKIN-111 - Getting issue details... STATUS   UICHKOUT-542 - Getting issue details... STATUS  CLOSED.
      • The Platform team will continue investigate perf optimisation of the authn/z subsystem through:  MODAT-51 - Getting issue details... STATUS , specifically:  OKAPI-770 - Getting issue details... STATUS
      • FOLIO-2296 - Getting issue details... STATUS  to help investigate perf problems
      • Pending perf problems to be addressed by other teams: 
      • Other perf issues:
        • MODINVSTOR-256 - Getting issue details... STATUS  still shows performance issues after RMB-468 updates, which seems to be related to reporting hit counts
    • UXPROD-1820 - Getting issue details... STATUS New development work (RMB 28.x related):
      • MODINVSTOR-349 - Getting issue details... STATUS  enabler for  UIIN-564 - Getting issue details... STATUS  is going to be addressed this week
  • Platform Q3.2 updates (devops):
    • FOLIO-2227 - Getting issue details... STATUS  pending completion on the following tasks:
    • Additionally the following CI problems are being addressed:
      • FOLIO-2280 - Getting issue details... STATUS  related to reference env security, BLOCKED on tasks to upgrade permission handling on individual modules
      • FOLIO-2218 - Getting issue details... STATUS  related to scaling issues caused by the increased CI/CD requirement
  • Q3.2 (Daisy) release:
    •  Hotfix release issues: (label ^q3.2-2019-hotfix^):
    • Getting issues...

Cate Boerema (Deactivated)

  • Chalmers is reporting lots of "items out of place" type issues such as:
    • Items that are showing up on the Hold shelf clearance report for one circ desk but aren't on the hold shelf.  These are sometimes found awaiting pickup on other service points or sometimes found.
    • Requests that are Closed - Filled with no evidence of a loan for that item for the requester
    •  Etc
  • Most of these are being reported via Slack channel and investigated by Cate
    • These are often difficult to debug - some observations from Chalmers can no longer be reproduced when checked (e.g. item no longer on Hold shelf clearance report or item status has changed)
    • Some are reproducable and bugs have been filed such as:
      • CHAL-85 - Getting issue details... STATUS  and  CIRC-516 - Getting issue details... STATUS  will need to be hotfixed when complete
      • UIIN-806 - Getting issue details... STATUS
      • CHAL-87 - Getting issue details... STATUS
  • Lots of Q4 work in progress but a significant number of features are at risk as they have been delayed and/or haven't started
    • Cap planning team will meet on Friday to discuss features likely to spillover
    • Cate will ask POs to tag items at risk

Getting issues...

Getting issues...

2019-10-15

Jakub Skoczen

  • Mid sprint 74
  • Platform Q3.2 updates (dev):
    • Security-related issues:
    • Performance-related issues:
      • UICHKIN-111 - Getting issue details... STATUS  IN REVIEW. Cate mentioned that she saw a visible improvement after the applying the latest round of hotfix releases. If the improvement is sufficient the issue can be closed. Similarly,  UICHKOUT-542 - Getting issue details... STATUS  may be reviewed again to verify if there's an improvement. The Platform team will continue perf optimisation of the authn/z subsystem through:  MODAT-51 - Getting issue details... STATUS  
      • Pending perf problems to be addressed by other teams: 
      • Next in-line, Platform team will work to reproduce check-in/check-out perf issues on the perf testing env:  CIRC-466 - Getting issue details... STATUS
      • UXPROD-1820 - Getting issue details... STATUS New development work (RMB 27.x related) has been resumed this week:
        • MODINVSTOR-256 - Getting issue details... STATUS  pending verification (on hold due to dev vacation)
        • MODINVSTOR-349 - Getting issue details... STATUS  enabler for  UIIN-564 - Getting issue details... STATUS  is nearing completion
  • Platform Q3.2 updates (devops):
    • FOLIO-2227 - Getting issue details... STATUS  pending completion on the following tasks:
    • Additionally the following CI problems are being addressed:
      • FOLIO-2280 - Getting issue details... STATUS  related to reference env security
      • FOLIO-2218 - Getting issue details... STATUS  related to scaling issues caused by the increased CI/CD requirement
      • FOLIO-2242 - Getting issue details... STATUS  related to the new model for configuring memory requirements of individual modules
  • Q3.2 (Daisy) release:
    •  Hotfix release issues: (label ^q3.2-2019-hotfix^):
    • Getting issues...

Cate Boerema (Deactivated)

  • Testing hotfixes for Chalmers issues:
    • CHAL-49 - Getting issue details... STATUS  - Hotfix has been applied to BF3.1 but it is difficult to test due to the below issues not yet being addressed.  Will finish testing when those fixes have been applied.
    • CHAL-54 - Getting issue details... STATUS  - Waiting for hotfix releases to be prepared and applied to BugFest 3.1 and 3.2
    • CHAL-52 - Getting issue details... STATUS  - Waiting for hotfix releases to be prepared and applied to BugFest 3.1 and 3.2
  • CHAL-79 - Getting issue details... STATUS  seems to have been addressed (cant repro in any local environments).  Need to decide if we want to hotfix to Chalmers for 3.1 or if they can wait for the upgrade next week
  • CHAL-43 - Getting issue details... STATUS  Waiting for "refined design" from Filip
  • Writing additional stories for  UXPROD-113 - Getting issue details... STATUS  as we have determined we need to introduce a new item and request status (this entails a significant amount of additional work)
  • Charlotte has supplied many new Inventory search and filter stories for the Core Functional team as part of UXPROD-140 - Getting issue details... STATUS .  Development will support searching and filtering by item and holding data but results are always instances (for now): https://docs.google.com/presentation/d/1HUX9ed0Qnx2jRE6M4DRlfTFUa-MUPJICD9k5lPECqew/edit#slide=id.g5dc4a09ded_0_0
  • Ann-Marie has written a number of stories for HRID handling across SRS, Batch import, Inventory and MARCcat: 
    • UXPROD-2114 for Inventory/Core-Fxn
    • UXPROD-2115 for SRS/Folijet
    • UXPROD-2116 for MARCcat/AtCult 

Getting issues...

Getting issues...

2019-10-08
  • Started sprint 74
  • Platform Q3.2 updates (dev):
    • Chalmers-related performance and stability issues:
      • mod-authtoken 2.3.0  and mod-permissions 5.8.3  released with performance improvement, available for both Q3.1 and Q3.2. Brings overall request time improvements, incl. Check-in/Check-out. To be verified on Bugfest environments when hotfixes are installed there.
      • UICHKIN-111 - Getting issue details... STATUS  back in OPEN for another review. Additional, tasks ongoing
        • MODAT-51 - Getting issue details... STATUS  reports ~35% request time spent in mod-authtoken/mod-permissions for a warm system with new improvements. Depending on trhe bugfest envs numbers, Platform team will look at additional improvements.
        • Problems to be addressed by other teams are still incomplete: 
        • The ticket to replicate check-in/check-out performance issues on the Perf test env by adding more realistic circulation data is pending:  CIRC-466 - Getting issue details... STATUS
      • UXPROD-1820 - Getting issue details... STATUS New development work (RMB 27.x related) has been resumed this week:
        • MODINVSTOR-256 - Getting issue details... STATUS  pending verification
        • MODINVSTOR-349 - Getting issue details... STATUS  enabler for  UIIN-564 - Getting issue details... STATUS  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:
    • FOLIO-2227 - Getting issue details... STATUS  which consists of the following sub-tasks:
    • Additionally the following CI problems are being addressed:
  • Q3.2 (Daisy) release:
    • Daisy out on 2nd October
    • Remaining problems will be addressed through hotfix releases. Jira tickets that should be addressed through hotfix releases will be labelled as ^q3.2-2019-hotfix^
    • Getting issues...
    • Proposal for Q3.2 bugfix/support release cycle:
      • continue publishing bugfix releases for issues tagged as ^q3.2-2019-hotfix^ until and including Jan 2020 (one month after Q4 is out)
    • What about Q3.1 bugfixes?
    • release spreadsheet: https://docs.google.com/spreadsheets/d/1DKV8rf3kD7QAz57etqA-C2FqHHLZmRVmMZFobvDszn8/edit#gid=0

Cate Boerema (Deactivated)

  • Nearly ready to hotfix 3.1 for Chalmers to address issues with Loans page when there are >100 loans
  • Matt Reno is working on another hotfix-worthy bug:  CHAL-49 - Getting issue details... STATUS
  • Filip is helping us to design a solution for  CHAL-43 - Getting issue details... STATUS
  • Review has been conducted of Tod Olsen's call number normalization code and it looks like FOLIO will be able to reuse it (may need a few adjustments first)
  • Otherwise, teams are progressing on Q4 MVP features and POs continue to write stories and ready the backlog

Getting issues...

Getting issues...

2019-10-01
  • Mid Sprint 73
  • Platform Q3.2 updates (dev):
    • Various security-related issues brought up last week took precedence over other work:
      •   OKAPI-763 - Getting issue details... STATUS  solution for  FOLIO-2287 - Getting issue details... STATUS
      • OKAPI-764 - Getting issue details... STATUS  solution for  FOLIO-2286 - Getting issue details... STATUS
      • RMB-478 - Getting issue details... STATUS
    • Chalmers-related performance and stability issues:
      • UICHKIN-111 - Getting issue details... STATUS  all individual backend tickets have been addressed (for list see previous report) besides:
        • MODAT-51 - Getting issue details... STATUS
        • MODPERMS-67 - Getting issue details... STATUS
        • MODUSERS-150 - Getting issue details... STATUS
        • Problems to be addressed by other teams are still incomplete:
        • The ticket to replicate check-in/check-out performance issues on the Perf test env by adding more realistic circulation data is pending:  CIRC-466 - Getting issue details... STATUS
      • UXPROD-1820 - Getting issue details... STATUS New development work (RMB 27.x related) has been resumed this week:
        • MODINVSTOR-256 - Getting issue details... STATUS  pending verification
        • MODINVSTOR-349 - Getting issue details... STATUS  enabler for  UIIN-564 - Getting issue details... STATUS  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:
    • FOLIO-2227 - Getting issue details... STATUS  which consists of the following sub-tasks:
    • Additionally the following CI problems are being addressed:
  • Q3.2 (Daisy) release:
    • release pending on a bugfix for  UIU-1271 - Getting issue details... STATUS  which should be available related today
    • during  UIU-1271 - Getting issue details... STATUS  another problem has been discovered,  STCOR-392 - Getting issue details... STATUS , 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:  Getting issues...
  • Have created first pass at release notes accessible from here: Release Notes
  • Q3 needs to be wrapped up in JIRA.  There are still ~10 open UXPRODs

Getting issues...

Getting issues...





  • No labels