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 4
Next »
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 |
|---|
|
| Functional | NFR |
|---|
| 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):
| | |
| 2019-08-13 | | | |
| 2019-08-06 | | |
Getting issues...
|
| 2019-07-30 | 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
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:
| | |
| 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 (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):
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)
| | |
| 2019-07-09 | Jakub Skoczen - Mid sprint 67
- Platform Q3.1 updates:
Cate Boerema (Deactivated) - 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?
| | |
| 2019-07-02 | 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
- Platform Q2.2 summary:
- Platform Q3.1 plans:
| | |
| | | |