Time/Place

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

Attendees 

Apologies:

**Each week a meeting chair will be assigned based on a rotating schedule.**

(star) - denotes note taker

Agenda

  1. Announcements:
  2. Pop-up/Other Topics:
    1. Slack Question: Will Hikari wait with FailFast=false? See https://fedora-project.slack.com/archives/C8B5TSR4J/p1716900977642069
  3. Migration Updates:
  4. Updates on:

REMINDER: Need to put tickets in meeting notes to ensure we don't lose information from dynamic filters.

    1. Open Tickets (but assigned in some cases): 

      T Key Summary Assignee Reporter P Status Resolution Created Updated Due
      Loading...
      Refresh

    2.  In Progress and older but still relevant open tickets:
       

      T Key Summary Assignee Reporter P Status Resolution Created Updated Due
      Loading...
      Refresh

    3. In Review:

      T Key Summary Assignee Reporter P Status Resolution Created Updated Due
      Loading...
      Refresh

    4. Recently closed tickets:  I set a filter on this for "closed" within "the last 2 weeks" - is this what we were thinking?

T Key Summary Assignee Reporter P Status Resolution Created Updated Due
Loading...
Refresh

Add filter for recently closed tickets (with 2 week timeline)?  Or just track what was done?



  1. Backlog Tickets to consider working:
  2. Next Meeting Chair:  
    1. Chair: Dan Field
    2. Note Taker: James Alexander

See Rotating Schedule here  

Notes

  1. Announcements
    1. Very hot in Moncton
  2. Slack
    1. HikariCP resolved by Demian - configuration is available here https://github.com/brettwooldridge/HikariCP#gear-configuration-knobs-baby
    2. Flyway update was merged with the ocfl-java 2.1.0
    3. Migration validator from Fedora 4 to 6? Josh working with Vanderbilt is also interested.
  3. Migration updates
  4. Tickets
    1. FCREPO-3945 - Getting issue details... STATUS - Updating the registration URL, nothing before 2020 was brought over. Wanting to clean up the data. Please re-register if you are an old user.
    2. FCREPO-3858 - Getting issue details... STATUS - Closed
    3. FCREPO-3784 - Getting issue details... STATUS - Still valid for the next Camel Toolbox update
    4. FCREPO-3776 - Getting issue details... STATUS - Still valid but there is an Auto-versioning page that contains some of this information, perhaps just a rename and some re-working of the existing content.
    5. FCREPO-3762 - Getting issue details... STATUS - Still a worthwhile task, there is a good basis in the fcrepo-camel-toolbox. 
    6. FCREPO-3935 - Getting issue details... STATUS - Ready for review
    7. FCREPO-3946 - Getting issue details... STATUS - Ready for review
    8. FCREPO-3941 - Getting issue details... STATUS - Started, Mike is going to add the 409 Conflict response and any other
    9. FCREPO-3939 - Getting issue details... STATUS - Needs a rebase
    10. FCREPO-3919 - Getting issue details... STATUS - No updates
    11. FCREPO-3917 - Getting issue details... STATUS - No updates
    12. FCREPO-3912 - Getting issue details... STATUS - No updates
  5. Budget for Mike's work has not been renewed and as such he will not be working on Fedora. Dan will be increasing his time from 50% to 80%.
  6. Fedora 7 needs to be a major version change as Spring 6 requires Java 17.
  • No labels