Skip to end of banner
Go to start of banner

FOLIO Q3 2019 (Daisy) Weekly Status Report

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 72 Next »


Suggest ideas for FOLIO reports and dashboards here

Getting issues...

Dynamic release data with weekly status updates

Q3 2019 Features in JIRA (updates dynamically)

Functional Features Today


Getting issues...

NFRs (Non-Functional Requirements) Today

Getting issues...

See the Q3 2019 Dashboard and the Chalmers Release Dashboard in JIRA for more charts and click-through to feature details.

See /wiki/spaces/DQA/pages/2654395 for bi-weekly updates on software quality.

Weekly Updates

Report Date

Overall Status Update

Q3 Feature Count on Report Date



Functional

NFR

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:
    • 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


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...

2019-09-24

Jakub Skoczen

  • Started Sprint 73
  • Platform Q3.2 updates (dev):
    • UXPROD-1820 - Getting issue details... STATUS  RMB 27.x related:
      • RMB-468 - Getting issue details... STATUS  enabler for  MODINVSTOR-256 - Getting issue details... STATUS  has been completed and awaits roll-out this sprint 
      • MODINVSTOR-349 - Getting issue details... STATUS  enabler for  UIIN-564 - Getting issue details... STATUS  requires functionality that was missing from  RMB-385 - Getting issue details... STATUS 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:
      • UICHKIN-111 - Getting issue details... STATUS  has been broken down into a set of analysis tasks last sprint: 
      • 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.
        • MODUSERS-150 - Getting issue details... STATUS
        • MODPERMS-66 - Getting issue details... STATUS
        • MODAT-49 - Getting issue details... STATUS
        • MODAT-51 - Getting issue details... STATUS
        • MODCAL-50 - Getting issue details... STATUS  (this problem has surfaced during check-out, not check-in, see UICHKOUT-541)
        • Problems to be addressed by individual teams:
      • 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) 
      • Stability problems being addressed:
  • 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:

Cate Boerema (Deactivated)

  • Loan policy testing in BugFest was blocked until today due to  CIRC-461 - Getting issue details... STATUS  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://issues.folio.org/secure/RapidBoard.jspa?rapidView=130
  • One more hotfix coming soon for Chalmers to address  CHAL-29 - Getting issue details... STATUS  and  CHAL-30 - Getting issue details... STATUS
  • 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:  UIIN-725 - Getting issue details... STATUS

Getting issues...

Getting issues...

2019-09-17

Jakub Skoczen

  • Mid Sprint 71
  • Platform Q3.2 updates (dev):
    • UXPROD-1820 - Getting issue details... STATUS  RMB 27 released, ongoing work in particular modules to roll out new functionality:
      • RMB-385 - Getting issue details... STATUS  enabler for  MODINVSTOR-349 - Getting issue details... STATUS  which in turn addresses  UIIN-564 - Getting issue details... STATUS
      • RMB-468 - Getting issue details... STATUS  enabler for resolution of following perf issue:  MODINVSTOR-256 - Getting issue details... STATUS  
    • Remaining Chalmers-related issues:
      •  brought up today by Cate, to be discussed at Platform's standup
      • UICHKIN-111 - Getting issue details... STATUS  has been broken down into following optimization tickets:
  • Platform Q3.2 updates (devops):
    • Focus on Daisy release activities
    • UXPROD-1827 - Getting issue details... STATUS
      • FOLIO-2011 - Getting issue details... STATUS  will be showcased at the PO meeting on Wednesday
      • Remaining FOLIO-1827 blockers:
      • FOLIO-2252 - Getting issue details... STATUS  
      • FOLIO-2056 - Getting issue details... STATUS , which is blocked on:
      • FOLIO-2227 - Getting issue details... STATUS  to be addressed in sprint 72
  • Q3.2 (Daisy) release:

Cate Boerema (Deactivated) 

Development:

  • Have hotfixed several bugs for Chalmers:  Getting issues...
  • Still working through several important issues:
    • CIRC-440 - Getting issue details... STATUS  - Development complete.  Testing in folio-snapshot now (looks good so far!)
    • UICHKIN-111 - Getting issue details... STATUS  - 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: Performance requirements for daily operation of the FOLIO system 
    • UIIN-687 - Getting issue details... STATUS  - Work Ryan did to  STCOR-388 - Getting issue details... STATUS  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:
    • CHAL-29 - Getting issue details... STATUS
    • CHAL-30 - Getting issue details... STATUS

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  CHAL-29 - Getting issue details... STATUS  and  CHAL-30 - Getting issue details... STATUS  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.    


Getting issues...

Getting issues...

Click to view status update history

Q3 2019 Release Features (Functional) by Status

Getting issues...

The Jira server didn't understand your search query. If you entered JQL, please ensure that it's correctly formed. If you entered an issue key, ensure that it exists and you have permission to view it.

Q3 2019 Release Features (NFR) by Status

Getting issues...

The Jira server didn't understand your search query. If you entered JQL, please ensure that it's correctly formed. If you entered an issue key, ensure that it exists and you have permission to view it.

Status

Definition

Open 

Feature is waiting to be picked up by PO.  

Draft 

Feature is  being worked on by the PO.  Discussions are happening with the SIGs and sub-groups, mock-ups are being created.  Analysis is underway.

Analysis Complete

PO analysis is complete.  Stories are written and mockups have been created.

In Progress

Analysis is complete and development is underway.  While it is often the case that we begin development on some aspects of a feature before the PO’s analysis work has been completed, please do not move a feature into Development (In Progress) until after Analysis is Complete.  This is important so we can maintain visibility into what features that have remaining PO work.

In Review

Most or all stories in the feature are In Review (being tested).

Closed

All stories in the feature have passed test and are closed.  Feature is complete.

Product Owner Updates


DateProduct OwnerNotable Risks, Issues and/or Changes
8/1/19Ann-Marie Breaux (Deactivated)Closed 2 features: UXPROD-1447 (block edit of Inventory Instances with underlying MARC Bib in SRS) and UXPROD-1220 (Assign tags to Data Import profiles)
8/15/19

Dennis Bridges

The following mvp features were closed: UXPROD-1603, UXPROD-717, UXPROD-721, UXPROD-719, UXPROD-1776, UXPROD-1665, UXPROD-189 see list

Following Cap plan updates I have removed the Q3 2019 fixed version from all features not marked as cap-mvp in order to clarify what will be delivered in Q3. This includes: UXPROD-204, UXPROD-194, UXPROD-1018, UXPROD-1036, UXPROD-1025, UXPROD-1564 see list

The Q3 2019 fixed version has also been removed from issues that are still currently in draft, as analysis and creation of user stories is ongoing and development work will not begin in Q3. This includes: UXPROD-689, UXPROD-1578, UXPROD-1547, UXPROD-697 see list

9/30/19Ann-Marie Breaux (Deactivated)

UXPROD-1124 (Assign tags to finance records): no work done in Q3, since the finance records structures were evolving; moved the whole feature to Q4

Split the following Q3 features:

UXPROD-255 (Filter by tags) is followed by UXPROD-2090 (Tags cleanup)

UXPROD-1125 (Assign tags to order records); backend work completed in Q3, to be followed in Q4 by UXPROD-2073 (Assign tags to order records and filter by them)

UXPROD-1379 (CRUD for action profiles) is followed by UXPROD-2074 (Bring action profiles to life)

UXPROD-1380 (CRUD for field mapping profiles) is followed by UXPROD-2075 (MARC field mapping profile details)

UXPROD-1768 (NFR Data Import work in Q3) is followed by UXPROD-2076 (NFR Data Import work in Q4)

UXPROD-1769 (Remaining job and match profile work) is followed by UXPROD-2077 (Part 2)

UXPROD-1805 (SRS MARC-Inventory Instance refinement) is followed by UXPROD-2078 (Last bits)














Click to view product owner update history

Chalmers 

One focus of Q3 2019 is delivering the features required by Chalmers to go live.  For this reason, we will take a closer look at those features in this portion of the report.  See the Chalmers Release Dashboard in JIRA for these and more click-through reports.


NOTE: There are also  Getting issues...  (UXPROD features) that have not yet been ranked by Chalmers.  As these features are ranked, we should expect the features needed below to increase.


Remaining Features Needed by Chalmers to Go-Live 

Unable to render Jira chart macro due to an execution error.

Chalmers for Go-Live Feature With No PO

key summary fixversions epic link
Refresh

Features Needed by Chalmers for Go-Live

The Jira server didn't understand your search query. If you entered JQL, please ensure that it's correctly formed. If you entered an issue key, ensure that it exists and you have permission to view it.



Q3 2012 Release History

MetricDescription
Current featuresFeatures targeted for Q3 release as of today
  • Getting issues... Functional
  • Getting issues... NFR
Baseline release features

Baseline features targeted at beginning of quarter (July 2, 2019)

  • Getting issues... Functional
  • Getting issues... NFR

  • No labels