Time/Place

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

Attendees 

Agenda

  1. Back-porting namespace prefix fix to 4.7.x?  Unable to locate Jira server for this macro. It may be due to Application Link configuration.

  2. Upcoming "Alignment to Spec" sprint
    1. Thoughts on backwards compatibility of deprecated API?
    2. Changing version in 'master' pom.xml from 4.8.0-SNAPSHOT to 5.0.0-SNAPSHOT?
  3. Tickets/PRs that need merging:
    1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.  - PR#1213 (4.7-maintenance cherry-pick)
    2. Unable to locate Jira server for this macro. It may be due to Application Link configuration.  - PR#1220 (4.7-maintenance cherry-pick)
  4. Progress on: Possible messaging memory leak?  
  5. 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
  6. LTS policy proposal
  7. Wrapping up fcrepo-import-export-verify: https://github.com/fcrepo4-labs/fcrepo-import-export-verify/pull/48
  8. Next week's facilitator?
  9. ...

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

Minutes

  1. Backporting user-supplied namespace fix to 4.7.x?
    1. Not in 4.7.4 because we thought it was a breaking change
    2. Maybe it's not breaking after all, and we can include in 4.7-maintenance
    3. We should do a sanity test to make sure
    4. Esmé Cowles: I'll do that
  2. Upcoming API spec alignment sprints
    1. Breaking changes coming, can we create a deprecated, backwards-compatibile API?
      1. Probably more trouble than it's worth
      2. Versioning is very different, hard to reconcile old and new API
      3. As the spec moves forward, we can revisit and see if it's feasible — and if we have the resources to support this work
      4. LTS makes breaking changes more acceptable, since users will have a supported 4.7.x release to use
    2. We should change master version to 5.0.0-SNAPSHOT, to avoid confusion about 4.7.x LTS
      1. We may want to have Jenkins build 5.0.x and 4.7.x snapshots to make it easier for people to use 5.0.x snapshot builds, but also allow 4.7.x snapshots for bugfixes in 4.7-maintenance
      2. We'll need to update related modules (auth, etc.) that are released in tandem (see spreadsheet)
      3. We should revisit which of these modules are going to be supported going forward, and whether we want to fold fcrepo-auth-webacl into the core codebase.
  3. Tickets that need attention
    1. Easy-to-review PRs (backports of commits from master to 4.7-maintenance)
    2. Aaron Birkland has been looking at https://github.com/fcrepo4/fcrepo4/pull/1220, but there are still some SSL issues with Chrome (vague error message), still investigating.
    3. Jared Whiklo will review https://github.com/fcrepo4/fcrepo4/pull/1213 once it's no longer out of date.
  4. Memory leak
    1. Peter Eichman is seeing stuck threads with large loads, despite increasing VM and Java RAM, etc.
      1. Looks like Modeshape event buffer is filling up
      2. Maybe the issue is Tomcat?  Or Tomcat's logging infrastructure? Not yet — have turned off indexing, but that didn't resolve the issue
        1. Might be worth trying latest Tomcat 8, or Jetty, even one-click JAR
        2. Or Modeshape 5.4 (4.7.4 is using 5.3)
        3. Tomcat's StuckThreadDetectionValve has some settings that might be relevant, such as minimum time before interrupting stuck thread
  5. Volunteer to facilitate next week
    1. Jared Whiklo can do it
  6. Time to first byte:  Unable to locate Jira server for this macro. It may be due to Application Link configuration.
    1. Any volunteers to tackle this? There is a solution outlined in the ticket
      1. Danny Bernstein may take a look at it

Action Items

  • No labels

All content on the LYRASIS Wiki is licensed under the CC BY (Attribution) license, unless otherwise noted.