Time/Place

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

Attendee

  1. Danny Bernstein 
  2. Jared Whiklo   
  3. David Wilcox 
  4. Andrew Woods 
  5. Ben Pennell(star)
  6. Peter Eichman
  7. Bethany Seeger
  8. Aaron Birkland
  9. Yinlin Chen

Agenda

  1. Announcements
  2. 5.0.3 and/or Fedora 5.1.0  updates
    1. In-Review:
      1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      2. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
    2. 5.1.0 Closed
      1. 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.

    3. 5.1.0 Open (need to re-evaluate for inclusion in 5.1.0):
      1. 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.

    4. 5.x-maintenance branch does not currently have the above completed changes.
  3. Next Steps for Fedora 6
    1. Java 11?
  4. Import  / Export
  5. <your discussion point here>

Tickets

  1. In Review

    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.

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

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

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

Notes

Announcements

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

  • Unable to locate Jira server for this macro. It may be due to Application Link configuration.
    • 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
  • 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 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. 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.
    • Unable to locate Jira server for this macro. It may be due to Application Link configuration. Bethany will double check this is still an issue. We may not be able to fix it still due to the Jena.
  • Documentation tickets
    • Unable to locate Jira server for this macro. It may be due to Application Link configuration.  is a meta issue
    • Unable to locate Jira server for this macro. It may be due to Application Link configuration. 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



  • No labels