Skip to end of metadata
Go to start of metadata

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

Report Date

Overall Status Update

Q1 Feature Count on Report Date



FunctionalNFR
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

  • 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

  • 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 

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

2019-09-10

Jakub Skoczen

  • Sprint 71
  • Platform Q3.2 updates (dev):
    • UXPROD-1820 - Getting issue details... STATUS  RMB 27, more releases last sprint, new features completed and more in progress
      • RMB-385 - Getting issue details... STATUS
      • RMB-457 - Getting issue details... STATUS
      • RMB-468 - Getting issue details... STATUS  potential solution for the following perf issues:
    • Chalmers-related issues:
      • CIRC-447 - Getting issue details... STATUS  solution for  UIREQ-335 - Getting issue details... STATUS
      • OKAPI-759 - Getting issue details... STATUS
      • OKAPI-760 - Getting issue details... STATUS
      • MODUSERS-147 - Getting issue details... STATUS  brought up today by Cate, to be discussed at Platform's standup
      • UICHKIN-111 - Getting issue details... STATUS  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):
  • Q3.2 (Daisy) release:

Cate Boerema

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

Getting issues...

Getting issues...

2019-08-27

Jakub Skoczen

  • Sprint 71
  • Platform Q3.2 updates (dev):
    • UXPROD-1820 - Getting issue details... STATUS  RMB 27 initial release performed last week, includes clean-up and bugfixes for RMB26 series, new functionality:
      • RMB-459 - Getting issue details... STATUS  
        which (once RMB27 is rolled out to storage modules, see MODUSERS-142 - Getting issue details... STATUS  and MODINVSTOR-342 - Getting issue details... STATUS ) will address  FOLIO-2102 - Getting issue details... STATUS
      • RMB-452 - Getting issue details... STATUS
      • RMB-451 - Getting issue details... STATUS
      • Many other fixes, full list here:  Getting issues...
      • tickets that are in the pipeline for the next RMB27.x releases:
        • RMB-454 - Getting issue details... STATUS
          RMB26 regression, not critical for existing functionality 
        • RMB-385 - Getting issue details... STATUS
        • RMB-457 - Getting issue details... STATUS
          helper utility to address remaining performance problems:  MODINVSTOR-256 - Getting issue details... STATUS  and  MODINVSTOR-336 - Getting issue details... STATUS
  • Platform Q3.2 updates (devops):
    • UXPROD-1827 - Getting issue details... STATUS
      • FOLIO-2011 - Getting issue details... STATUS
        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  FOLIO-2227 - Getting issue details... STATUS )
      • Remaining FOLIO-2011 blockers: 
      • FOLIO-2194 - Getting issue details... STATUS
      • FOLIO-2056 - Getting issue details... STATUS
      • FOLIO-2217 - Getting issue details... STATUS
    • UXPROD-1815 - Getting issue details... STATUS
  • Scaling FOLIO development process:
  • Q3/Q4 platform features in DRAFT (requirements and design):

Getting issues...

Getting issues...

2019-08-13

Jakub Skoczen

  • Sprint 70
  • Platform Q3.2 updates:
    • General platform bugfixes for Q3.2:
      • FOLIO-2102 - Getting issue details... STATUS  Spike: timestamp metadata missing from bootstrap data (spillover)
    • UXPROD-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 (
      • MODINVSTOR-292 - Getting issue details... STATUS
      • RMB-411 - Getting issue details... STATUS  
      • RMB-432 - Getting issue details... STATUS
      • completed large new functionality  RMB-395 - Getting issue details... STATUS  which will help address remaining performance issues (filtering by location and status)
    • UXPROD-1827 - CI-integrated continuous deployment (Q3, FOLIO setup) IN PROGRESS 
  • Platform Q3.2 work:
  • Q3.1 Release Management:
  • Scaling FOLIO development process:


Getting issues...

Getting issues...

2019-08-06

Jakub Skoczen

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

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

  • 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

Getting issues...

Getting issues...


2019-07-30

Cate Boerema

  • 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  UXPROD-1653 - Getting issue details... STATUS which has proved a very complex feature to develop
      • Must fix for Q3.2:  CIRCSTORE-142 - Getting issue details... STATUS   (I would caution Chalmers against using this feature until these bugs have been addressed)
      • Nice to have:  UIREQ-294 - Getting issue details... STATUS  
    • General UI performance issues ( STCON-85 - Getting issue details... STATUS ) 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:
      • MODINVSTOR-319 - Getting issue details... STATUS  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.
      • RMB-432 - Getting issue details... STATUS  and  RMB-438 - Getting issue details... STATUS , 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  UIREQ-295 - Getting issue details... STATUS  / CIRCSTORE-138 - Getting issue details... STATUS we decided to expedite a fix for this issue through  RMB-439 - Getting issue details... STATUS
      • FOLIO-2102 - Getting issue details... STATUS
    • UXPROD-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  FOLIO-2176 - Getting issue details... STATUS
        • RMB-395 - Getting issue details... STATUS  is developed to address two remaining perf test issues:  MODINVSTOR-256 - Getting issue details... STATUS  and  MODINVSTOR-292 - Getting issue details... STATUS  
    • UXPROD-1827 - CI-integrated continuous deployment (Q3, FOLIO setup) IN PROGRESS 
  • Platform Q3.2 work:
    • UXPROD-1815 - support for upgrading schemas without complete reload of data (DB migrations)IN PROGRESS
      • FOLIO-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:
  • Scaling FOLIO development process:

Getting issues...

Getting issues...

2019-07-16

Jakub Skoczen

  • Started sprint 68
  • Platform Q3.1 updates:
    • General platform bugfixes critical for Q3.1:
      • MODAT-47 - Getting issue details... STATUS  which addresses the problem reported in  CIRC-379 - Getting issue details... STATUS  a Pull Request is ready but requires refactoring
    • UXPROD-1818 - Getting issue details... STATUS
      • Most UI bugs resolved (confirmed) or reassigned to front-end developers (Core: functional), one remaining:
        • RMB-432 - Getting issue details... STATUS
      • Continued focus on performance testing and tuning:
        FOLIO-2143 uncovered some performance issues which have been addressed in Sprint 67
        • RMB-429 - Getting issue details... STATUS
        • RMB-417 - Getting issue details... STATUS
      • and some bugs that are being addressed this sprint:
        • RMB-430 - Getting issue details... STATUS
      • 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:
        • RMB-395 - Getting issue details... STATUS  likely shipped in RMB 27 to address the remaining perf issues (item.barcode and holdings.location search)
    • UXPROD-1827 - Getting issue details... STATUS
      • AWS/EKS cluster set up tasks completed (including ingress and Ansible roles)
      • FOLIO-2055 - Getting issue details... STATUS  to be completed this week
      • Added several SPIKEs this sprint for remaining issues:
  • Platform Q3.2 work already begun:
    • UXPROD-1815 - Getting issue details... STATUS
      • FOLIO-2169 - Getting issue details... STATUS  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:

Cate Boerema

  • 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):  STCON-85 - Getting issue details... STATUS   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:  STSMACOM-229 - Getting issue details... STATUS   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:  CIRC-390 - Getting issue details... STATUS
    • 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)

Getting issues...

Getting issues...

2019-07-09

Jakub Skoczen

Cate Boerema

  • All Core Functional must-haves for 3.1 are In review or In progress: https://issues.folio.org/secure/Dashboard.jspa?selectPageId=10628
  • Moving requests from one item to another is tracking for completion
  • Also making progress on Inventory cleanup (adding controlled vocabularies, notes etc.)
  • Fixing some critical Inventory search bugs with lots of help from Core Platform
  • Added release notes and stats from Q2: Release Notes
  • Capacity planning team working through process for MVP proposal
    • Have discussed assignment for POs (will share with them at PO meeting tomorrow)
    • Harry has put together a good deck on goals and process
  • SIGs continue to do re-ranking - lots of good discussions and many things are being considered lower priority than previously ranked.  Ranks are not always being updated in JIRA perhaps due to organizational process delays?

Getting issues...

Getting issues...

2019-07-02

Cate Boerema

  • 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

Getting issues...

Getting issues...





  • No labels