...
Please squash a bug!
Expand Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery filter=13122 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 Tickets resolved this week:
Expand Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery filter=13111 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 Tickets created this week:
Expand Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery filter=13029 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5
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.