Page History

• Attendees / Apologies
• Upcoming Availability

Consistent Dev Environment

Aditya matukumalli to add workspace setup guide to ensure consistency in local test & development environments

• • some reported issues that may need this to be reviewed
    • Claudia: length of time to build environment recently (looks like a package manager issue, or local issue)
    • Peter: test coverage is reported incorrectly when run inside workspace ()
    • Ethan: some additional scripts used did not encode correctly when moving from Windows to Linux, plus folio-erm-usage is broken 
  • shouldn't need to add new documentation
    • Stripes Environment Setup is FOLIO standard guide https://github.com/folio-org/stripes-cli/blob/master/doc/user-guide.md#platform-development
    • Then there are some ERM variations, that relates to erm-platform, documented in github (
    cf
    • https://github.com/folio-org/
    stripes-cli/blob/master/doc/user-guide.md#platform-development)
    • can be point 
    • platform-erm)
  • registry should point to FOLIOCI (npm-folioci, not npm-folio)

Release Candidates

Code Review: 

• NA

QA / UAT 

• NA

For Release

• NA

Items at Risk / Spillover

In Progress

• Jira
  server FOLIO Issue Tracker serverId 6ccf3fe4-3301-368a-983e-20c466b11a49 key ERM-1239

  • Previously:
  • Various unexpected errors when using stripes clean - cleanup of workspace is hanging
  • May need to use console to interactively select stripes version rather than from script
  'Contain' error which may be resolved with the 
  • needed to add a couple of arrow brackets
  • now resolved
  • Other issues with adding edit license and amendments
    • shortcut to edit license not working, is handled differently for agreements
  • Gill Osguthorpe to separate issue for licenses and amendments to avoid holdup
    • amendments shortcuts to be returned to backlog for now

• Jira
  server FOLIO Issue Tracker serverId 6ccf3fe4-3301-368a-983e-20c466b11a49 key ERM-1240

  • picked up to test contain error - confirmed
  • easier, so prioritising over licenses
• RTL Test Conversion:

  • Jira
    server FOLIO Issue Tracker serverId 6ccf3fe4-3301-368a-983e-20c466b11a49 key ERM-1281

    • sample test created and passed, so no issues with making progress
    • some suggestions to improve test structure relating to translation

  • Jira
    server FOLIO Issue Tracker serverId 6ccf3fe4-3301-368a-983e-20c466b11a49 key ERM-1274

    • got the first two big issues done now
    • rest should be straightforward
    • looking to resolve 

• Jira
  server FOLIO Issue Tracker serverId 6ccf3fe4-3301-368a-983e-20c466b11a49 key ERM-1528

  / 

  Jira
  server FOLIO Issue Tracker serverId 6ccf3fe4-3301-368a-983e-20c466b11a49 key ERM-1529

  • Previously
    • EF should have repo setup permissions
    • aim to develop skeleton apps on Thursday
    • then to follow up with Ian on backend design / model, including suggestion posted as comment to 1529
  • unblocked to progress
  • not actively progressing until there is development content

• Jira
  server FOLIO Issue Tracker serverId 6ccf3fe4-3301-368a-983e-20c466b11a49 key ERM-1532

• • working locally but failing tests

• Jira
  server FOLIO Issue Tracker serverId 6ccf3fe4-3301-368a-983e-20c466b11a49 key ERM-12411534

  /

  Jira
  server FOLIO Issue Tracker serverId 6ccf3fe4-3301-368a-983e-20c466b11a49 key ERM-15271531

  • needs to be merged together with 1532 t avoid conflicts or failures
  • more stripes workspace issues
    • EF to liaise with AM to resolve
  • should be

Sprint Backlog

• Jira
  server FOLIO Issue Tracker serverId 6ccf3fe4-3301-368a-983e-20c466b11a49 key ERM-15311241

   

• Jira
  server FOLIO Issue Tracker serverId 6ccf3fe4-3301-368a-983e-20c466b11a49 key ERM-15341527

  • Peter to pick up next

Needs Elaboration

• Jira
  server FOLIO Issue Tracker serverId 6ccf3fe4-3301-368a-983e-20c466b11a49 key ERM-1459

  • dev wants more generic test descriptions to devise code tests from

New Issues

Added to sprint