Versions Compared

Key

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

...

  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

Actions

  1. Announcements
    1. Fedora 6.0 release
      1. Planning to release early next week
    2. Release Party
      1. Informal gathering to celebrate the release
      2. Likely in the next 3-4 weeks
    3. Migration workshop
      1. Taking place on Tuesday
      2. More technical workshop, using migration-utils, migration-validator, fcrepo-docker, etc.
  2. Testing
    1. migration-utils slow-down update
      1. Issue seems to have been resolved
      2. OCFL object session has a cache for resource headers that migration-utils wasn't using
        1. Updating a binary or its description touches the header for its counterpart
        2. Migrating multiple versions of the same object is problematic because new OCFL object sessions are created which requires reading headers
        3. Peter introduced a new cache that mitigates this
      3. NAS also performs inconsistently
      4. Changes are in fcrepo-storage-ocfl
  3. Release Candidate updates
    1. https://github.com/fcrepo/fcrepo/pull/1922: search optimization saga
      1. Changes to MySQL undid some work we did to optimize Postgres
        1. Danny updated the PR to fix this
    2. https://fedora-repository.atlassian.net/browse/FCREPO-3734: support for multi-architecture builds in the CI pipeline
      1. Change in fcrepo-docker and fcrepo
      2. Docker pull automatically grabs the appropriate image based on processor architecture
    3. https://fedora-repository.atlassian.net/browse/FCREPO-3620: Fedora 5 -> 6 upgrade fails if a Fedora 5 export has retrieved the external binaries
      1. Mike is working on this one
      2. Almost ready for review
    4. https://fedora-repository.atlassian.net/browse/FCREPO-3735: Add java option to make the rebuild run asynchronously 
      1. UVA is experiencing an extremely slow rebuild in their AWS environment
      2. This change would allow metrics to be viewed while a rebuild is happening - otherwise metrics can't be viewed until the completion of the process
      3. Could be a dangerous change - need to make sure write operations are not possible during the index rebuild
      4. UVA rebuild is finished so we can check in on their performance and revisit this issue later
  4. Release timing
    1. Due to recent changes we will cut another RC and delay the release by 1 week
  5. fcrepo 5 release
    1. Artifacts were deploying to Sonatype but Javadocs are not building
    2. Ben is looking into this
  6. Fedora 6.0 release dependencies
    1. RC uses snapshots of dependencies but these are packaged with the release
    2. Code changes to main should not break RCs. Some of the new changes will break RC-1
    3. Going forward, these dependencies should also get RC releases so changes to main don't break a RC

Actions

  •  Look through migration util commits since December to see if there are any potential causes of performance drop off.
  •  cut the release candidate today
  •  Calvin will adjust the prometheus.yml targets line to point at the localhost fedora on port 8080 to run the metric on prometheus docker compose