Skip to end of banner
Go to start of banner

2019-05-01 ERM Delivery Weekly Update

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

Discussion items

TimeItemNotesAction Items
<5 minsIntroductions
  •  
30 minsDemos
  • In Development
  • In Code Review
  • In QA / Accepted
  •  
10 minsSprint Completion
  • Merge Cutoff
    • Friday 2pm UK
  • Items at Risk / Spillover
    • Error rendering macro 'jira' : Unable to locate Jira server for this macro. It may be due to Application Link configuration.
    • Unable to locate Jira server for this macro. It may be due to Application Link configuration.
    • Unable to locate Jira server for this macro. It may be due to Application Link configuration.
  •  
10 minsUpcoming SprintSee ERM Next Sprint Candidates list in https://issues.folio.org/secure/RapidBoard.jspa?rapidView=89&view=planning.nodetail
5+AOB
  • Previous Actions
    • Bootstrapping data:
      • taking it out of module to not require code changes but use data scripts
      • will still be an issue for bootstrapping users (ERM-49) - to be considered in ongoing conversations
    • Developer onboarding: 
  • 'Office hours' `carried over`
  • Changes to Team Updates in #erm-updates
    • no mid-day updates
  • FOLIO Meetup Washington 17-19 June
    • not having a fringe dev gathering
    • looking at doing this early Q3
    • date options TBC
  •  Set up onboarding feedback session for next week.


Sprint WIP Demos

Delivery Board: https://issues.folio.org/secure/RapidBoard.jspa?rapidView=89

FeatureIssueWhoNotes / TODO

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Unable to locate Jira server for this macro. It may be due to Application Link configuration.  

?

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Pending ERM-163

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Unable to locate Jira server for this macro. It may be due to Application Link configuration.


Stuck In Code Review because of build issue with GBV test

  • Progress to In QA for , testing on folio-snapshot or folio-testing.

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

  • PR to be submitted

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Determine where/how to  Unable to locate Jira server for this macro. It may be due to Application Link configuration.  

  • To store in db to circumvent OKAPI non-persistence issue.
  • Example
    • median individual file size: ~345kb
    • from Benjamin: 10 years, 1000 files, 800mb total
  • Some organizations may use cloud storage going forward
    • could be worth abstracting implementation from outset, but not to be done this time round

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

  • Final set of tests expected to be completed today

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Not progressed

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

?

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Integration tests are pending, but generator is finished.

  • PR to be submitted for work completed so far. 
  • Integration tests to be resolved separately.
  • No labels