You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

Time/Place

This meeting is a hybrid teleconference and IRC chat. Anyone is welcome to join...here's the info:

Attendees 

Agenda

  1. Upcoming "Alignment to Spec" sprint

  2. Progress on: Possible messaging memory leak?  
  3. Need volunteer for:  Unable to locate Jira server for this macro. It may be due to Application Link configuration.
    1. Solution is outlined in ticket
  4. LTS policy proposal
  5. Wrapping up fcrepo-import-export-verify: https://github.com/fcrepo4-labs/fcrepo-import-export-verify/pull/48
  6. Report on 4.7.4 Benchmarks and Testing (Carrick Rogers)
  7. Future of PairTrees and  https://github.com/fcrepo4/fcrepo4/pull/1223
  8. Status of "in-flight" tickets

    type key summary assignee reporter priority status resolution created updated due

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

Ticket Summaries

  1. Please squash a bug!

    key summary type created updated due assignee reporter priority status resolution

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

  2. Tickets resolved this week:

    key summary type created updated due assignee reporter priority status resolution

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

  3. Tickets created this week:

    key summary type created updated due assignee reporter priority status resolution

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

  4. Avalon R6 4.7.4 Testing

Minutes

Action Items

  • Sprint starting next week  - 
    • Danny Bernstein will not be available for the first day of sprint next week
  • Update on memory leak issue from Peter Eichman
    • modeshape bug - fixed in modeshape 5.4  been unable reliably get system to fail and hang in test case.   
    • With avoiding transaction rollbacks they were able to run the remainder of the load and it completed successfully. 
    • tested with batch loader? Not gotten back to that yet
    • ran into another issue which may or may not be related - there were some binaries where the metadata was there, but the binaries themselves were not in the system.  
      • binaries were probably large enough to not hit the 4k minimum size (repository.json config)
      • related to modeshape upgrade?  no, this was happening in the modeshape 5.3 system causing the failed transactions he was seeing
  • No labels