Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Announcements
  2. Testing
    1. UVA: slow rebuild issue
    2. migration-utils slow-down update
  3. What needs to happen before core RC?
    1. Outstanding bugs/issues
    2. Performance tests
  4. Camel Toolbox Update
  5. OCFL v1.0/v1.1 objects and  Fedora
  6. Pr-release short list of bug fixes and improvements
    1. https://fedora-repository.atlassian.net/browse/FCREPO-3620 : Fedora 5 -> 6 upgrade fails if a Fedora 5 export has retrieved the external binaries
  7. fcrepo 5 release
  8. fcrepo 6 jena upgrade issues - application/x-turtle
  9. Any other new tickets/issues to be considered for the release
  10. Your topic

...

  1. In Review

    Expand

    Jira
    serverDuraSpace JIRA
    jqlQueryfilter=13100
    serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5


  2. Please squash a bug!

    Expand

    Jira
    serverDuraSpace JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    maximumIssues20
    jqlQueryfilter=13122
    serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5


  3. Tickets resolved this week:

    Expand

    Jira
    serverDuraSpace JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    maximumIssues20
    jqlQueryfilter=13111
    serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5


  4. Tickets created this week:

    Expand

    Jira
    serverDuraSpace JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    maximumIssues20
    jqlQueryfilter=13029
    serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5


Notes

  1. Workshop was good, had 50 people attend.
  2. Service maintenance may have affected their system, unable to connect to the MySQL server for some reason. Both servers are running and Calvin was able to connect to the MySQL from the Fedora server (using the command line tool). setenv.sh has not changed.
  3. Release candidate : Suggested that we run some performance tests prior to cutting the RC. Any outstanding fixes. WebAC caching PR and updated dependencies.
    1. Do we want to support the application/x-turtle media type?
    2. Do some performance testing over the weekend and look to start the release candidate process next week.
  4. Camel-toolbox updates, Jared to help look at the failing unit tests in Danny's work.
  5. OCFL v1.0 → 1.1 changes. There is really no change to the spec that will affect much of anything, but it is a version change. So we could have two versions of objects in the same repository. Should old v1.0 object be left as the old version or should it be upgraded automatically. How does the upgrade work. You change the version identifier in the new version as well as the namaste file in the current version and copying that updated namaste to the root.
  6. Ben to do the Fedora 5 release, testing could draw in the Islandora 8 users to help out (hopefully)
  7. Announcements
    1. Fedora Workshop - Migration workshop, intermediary level but open to everyone. Helpful to have commandline and docker experience.
      1. Will use temporary fedora cloud instances for users
    2. Fedora Jira relocated to https://fedora-repository.atlassian.net/
  8. Steering update 
    1. Mostly reporting out on plan for release of Fedora 6
    2. Next steps will be determining what happens after Fedora 6 release
  9. Testing
    1. UVA: slow rebuild issue
      1. Very slow, looking into if there are any issues with AWS configuration particularly regarding initialization of the disk
    2. Whitman still doing ingest tests, focus is on the Islandora side. Trying to get stats on newspaper ingest.
    3. Things are generally looking good for Islandora, there will be a release coming up soon.
    4. migration-utils slow-down update
  10. Updates on the performance improvement work
    1. ACL Caching
      1. Work has stopped for the moment. May require duplicating code, or moving the cache to earlier in the stack. Mostly done, but tests not running yet.
      2. Could be move to a point release if necessary, but will attempt to finish up
    2. MySQL dead-lock and other bugs
      1. Fixed initial issue that Felix had → https://fedora-repository.atlassian.net/browse/FCREPO-3721
      2. There is an additional issue related to mysql case sensitivity in ids, in which fedora does not currently state a collation type for its tables which can result in the tables either being case sensitive or not.
        1. https://fedora-repository.atlassian.net/browse/FCREPO-3722
        2. Leaning towards having fedora set the collation by default, meaning users would have to override it after creation if they needed a different one. The alternative would be to document how users should set up their mysql db.
  11. Pr-release short list of bug fixes and improvements
    1. https://fedora-repository.atlassian.net/browse/FCREPO-3620 : Fedora 5 -> 6 upgrade fails if a Fedora 5 export has retrieved the external binaries
    2. https://fedora-repository.atlassian.net/browse/FCREPO-3672: Update fcrepo-java-client to run against Fedora 6 (done)
    3. De-OSGI-ify fcrepo-camel  (done)
    4. De-OSGI-ify camel toolbox  (in progress)
      1. Updating tests, turning into microservices
  12. Fcrepo 5 release
    1. Published 5.0.0 fcrepo-java-client version
    2. Modeshape update PR open → https://github.com/fcrepo-exts/modeshape/pull/8
    3. Will need to release the modeshape version, then do a point release of Fcrepo 5.1.x.
  13. Any other new tickets/issues to be considered for the release
    1. https://fedora-repository.atlassian.net/browse/FCREPO-3704
      1. Thomas has started looking at this, he has run into issues where their client gets stuck forever on requests. Could be related to creating new clients for each transaction rather than reusing the same client.
  14. Release Candidate
  15. Plan to cut the release sometime next week
  16. Need to finish the mysql bug fixes, and potentially finish the WebAC cache.

Actions

  •  Look through migration util commits since December to see if there are any potential causes of performance drop off.