Page tree
Skip to end of metadata
Go to start of metadata


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



  1. 4.7.4 release testing (4.7.4 JIRA tickets)
    1. Release planned for Aug 1

    2. Samvera and CLAW testing?
    3. Backwards-compatibility testing?
      1. Likely a breaking change that should not be in the 4.7.4 release:  FCREPO-2393 - Getting issue details... STATUS
  2. Fedora alignment to API sprints
  3. The divide between 4.7-maintenance and master branches
    1. Commits that are in 4.7-maintenance and should be in master:
  4. Working towards the next Import/Export release
    1. Ben PennellMichael Durbin? any word on  FCREPO-2459 - Getting issue details... STATUS
  5. Adjusting the approach to serving /fcr:assets. (github-pr)
  6. Now that the fcrepo-2508 is closed, any update on the related tickets:
    1. FCREPO-2516 - Getting issue details... STATUS  - likely resolved, waiting on feedback from Jose Blanco
  7. ...
  8. Status of "in-flight" tickets

    T Key Summary Assignee Reporter P Status Resolution Created Updated Due

Ticket Summaries

  1. Please squash a bug!

    Key Summary T Created Updated Due Assignee Reporter P Status Resolution

  2. Tickets resolved this week:

    Key Summary T Created Updated Due Assignee Reporter P Status Resolution

  3. Tickets created this week:

    Key Summary T Created Updated Due Assignee Reporter P Status Resolution


4.7.4 Release

  • Release candidate went out earlier this week
  • Attendees encouraged to run through tests
  • There have been many big fixes and improvements that have gone into master but have not come out in a point release
  • 4.7.4 makes these available in a backwards-compatible way
  • Need CLAW and Samvera tests
  • Consolidating Spring configuration could be a breaking change
    • Need to pull this commit out and tag RC2
  • Need better backwards compatibility testing
    • May involve existing data
    • May require an integration environment , sandbox style
    • We could automate the creation of resources in Fedora for this build process
    • Spin up a release candidate and feed it an import package
    • Provide recipes for different expectations/types of data

Fedora API alignment sprints

  • There is a delta between the current iomplemention of Fedora and the spec, which we need to close with these sprints
  • First sprint starts Sept. 11 for 2 weeks. Aaron Birkland will coordinate
  • Second sprint starts Sept. 26 for another 2 weeks
  • Interested folks are encouraged to sign up
  • We will also support/encourage other implementations to implement the spec. Need 2 or more to validate the spec

The divide between 4.7-maintenance and master branches

  • 4 commits in 4.7-maintenance and should be in master
  • These are revert commits for breaking changes that messed up namespaces for existing implementations

Working toward next import/export release

  • One ticket still in review
  • Ben P is making good progress on version import, but we needn’t wait on this issue to cut a release
    • We can always cut a new release when versioning import has been implemented
  • Call for volunteers to do the release
    • Danny B volunteered
    • Jared will help

Adjusting the approach to serving /fcr:assets

  • Issues with HTTPS
  • Seems to be an NGINX problem
  • Fixing this at the Fedora level would institutionalize a workaround
  • No labels


  1. Unknown User (acoburn)

    Related to serving the /fcr:assets point, this is not just an NGINX problem. The same issue applies equally to proxying with Apache httpd (I suspect that any reverse proxy would encounter the same issue).

    That is, I would not characterize fixing this as "institutionalizing a workaround" at all; rather, it is a problem with the Fedora software and it should be fixed. And the most effective fix will likely be to just use path-based URLs, which skirts the entire mixed protocol issue entirely. Alternately, a scheme-less URL would amount to the same thing, but a path-based URL will tend to be nicer for reverse proxies. 

  2. Exactly right.  I was on the call, but unfortunately was disconnected in the middle of making that point.  It is not an NGINX problem.  The pattern of using a SSL termination proxy is well-established and common, just not with Fedora yet. 


    Opened a new issue in Jira:

    FCREPO-2534 - Getting issue details... STATUS