...

1. In Review

   Expand
   Jira server DuraSpace JIRA jqlQuery filter=13100 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

   
   

2. Please squash a bug!

   Expand
   Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery filter=13122 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

   
   

3. Tickets resolved this week:

   Expand
   Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery filter=13111 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

   
   

4. Tickets created this week:

   Expand
   Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery filter=13029 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

   
   

Notes

Announcements

• DC Fedora User Group coming up soon, May 7 and 8. Will include an OCFL hack-a-thon.
  • Washington D.C. Area Fedora User Group Meeting and OCFL Hackathon: 7-8 May 2019

Maintenance branches

• At UMD use git flow model. Cut release branch, run tests, apply bug fixes. Then merge back into develop and stable branches (master in our case). Stable only updates when make release.
  • https://nvie.com/posts/a-successful-git-branching-model/
  • Can do long running branches, and feature branches off of these.
  • Separating out a branch that is stable and a branch that is development is valuable. Master is more like development at the moment for fcrepo, so could add a stable branch.
    • This could be helpful when blowing up fedora for v6.

Ticket updates/new issues

• Jira
  server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2991

  • Bess hasn't had time to look at it yet. Both Danny and Jared have
• Issue with windows file paths from tech mail list https://groups.google.com/forum/#!topic/fedora-tech/vUb13a7m__I
  • Aaron Birkland may be able to take a look at this next week. It stems from using Paths, which are not appropriate for URI manipulations in windows.
    • this probably needs to be fixed https://github.com/fcrepo4/fcrepo4/blob/master/fcrepo-kernel-modeshape/src/main/java/org/fcrepo/kernel/modeshape/services/TimeMapServiceImpl.java#L98
  • The reporter probably still needs a Jira account.
  • Not a lot of people using windows.
  • Could we add windows build to travis?
• Java 11
  • Javadoc failures
  • In maven source plugin, we specify 1.8
  • Wiremock needs to be updated for new versions of java
    • Some tests are sitting there forever waiting
    • A lot of thread errors
    • It is mainly used for external content unit tests.
    • Wiremock not compatible with java 11 because of ASM, can get past by including your own version of ASM
• Still need to decide if some of the open tickets are still an issue or something that we have any intention of addressing given that modeshape is going away
  • Such as

    Jira
    server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2092

  • Jira
    server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-1987

    seems significant, but was before the refactoring of how binaries and descriptions are stored
    • should we even allow hash uris on binaries? Seems like a modeling question.
      • UMD using hash uris to point to controlled vocab info and maintain link to original vocab uri. This could be happening off of the binary description in some use cases.
    • There's a bit of slipperiness in the code whether you get the binary or the description
    • This is probably not a candidate for 5.1, needs some reevaluation to determine if its still a problem, how it would be addressed, and a decision about if we want to support.
    • Are we aware of anyone in the community that is blocked by this? This issue may not be a thing anymore without modeshape. For issues like this, may be best to simply say that the complexity of resolving these issues in modeshape is not worthwhile without active immediate need.
    • Jared is going to test this one.

  • Jira
    server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-1799

    Bethany will double check this is still an issue. We may not be able to fix it still due to the Jena.
• Documentation tickets

  • Jira
    server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2784

     is a meta issue

  • Jira
    server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2647

    Mainly need to do a review of the documentation, it hasn't been done in a while. Some things are missing, like that you can POST sparql updates.
• Goal is to do 5.1 before OR. Who is doing the release?

Actions

•  Peter Eichman  is planning to work on documenting UMD's fixity check system on the  Fedora in Production: Case Studies wiki page.
•  Danny Bernstein will pull together some use cases for object locking in OCFL
•  Danny Bernstein to take first pass to quickly remove/clean-up obvious tickets labeled with "fixed version" 5.1.0
•  Bethany Seeger to review fcrepo-2902 (thanks Danny Bernstein )
•  Ben Pennell  to review fcrepo-2789
•  Jared Whiklo to fix Java 11 javadoc errors in a new ticket, link to fcrepo-2958
•  Danny Bernstein to rename 5.x-maintenance to 5.0.x-maintenance

...