Time/Place

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

Attendees

Agenda

  1. 4.7.5 release testing - discussion of where things stand
    1. FCREPO-2666
    2. FCREPO-2665
  2. Moving into alignment with the spec
    1. Sprint date options
  3. Pairtree/Appletree options
    1. Where did we land here? 
    2. Volunteer to create a JIRA to specify the solution.
  4. External Content: Redirect or Proxy? on fedora-tech
    1. Where is this landing?
  5. Unable to locate Jira server for this macro. It may be due to Application Link configuration.  - Also move forward with creation-side resolution?
  6. Compatibility Test Suite 
  7. OCFL Update/Discussion
    1. Andrew Hankinson's paper
  8. ...

Ticket Summaries

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

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

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

Minutes

1. Current RC has issues with MySQL and Postgres, but need more tests to further confirm it.
https://jira.duraspace.org/browse/FCREPO-2665: not make it a blocker
https://jira.duraspace.org/browse/FCREPO-2666: not make it a blocker
Aaron will work on API-X.
There will be RC3 soon.

2. The Fedora API Alignment Sprint Date Options poll will close tomorrow.

3. Still needs further discussions and testing about Pairtree/Appletree options. Some discussions list below.
1. Need to do some furthers testing to help determine these options that indeed help the performance issues.
2. Option 4 is specifically intended to remove the ability to use pairtrees for partitioning membership from the client side.
3. Go with option 3 allow people to configure pairtrees if they want to do that, but stop hiding them if they exist.
4. Implement a workaround solution sounds not right.
5. Should not be a default configuration.
6. Need a document for these behaviors.
7. What is the default behaviors we want to bring into Fedora 5?
8. Some people favor option 3.

Other agenda items move to next meeting.


  • No labels