...
Please squash a bug!
Expand Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 40 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 40 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 40 jqlQuery filter=13029 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5
Minutes
Release 4.5.1
- A Fedora 4.5.1 release is in process. A release candidate will be released tomorrow.
- Three weeks will be alloted for testing, after which the final version of 4.5.1 will be released.
- New features in development now should be put in the Dev branch.
- Support for building on Windows needed? Yes, a couple of people in the community will test a Windows build.
Pregnant pause while Andrew reconnects.
Release Testing
- Review of 4.5.1 Test Plan at https://wiki.duraspace.org/display/FF/Release+Testing+-+4.5.1
- There are 11 manual tests listed. An additional content negotiation test could be useful. This test could retrieve content in various RDF formats. Can we automate these tests?
Test Automation
- Perhaps a brief shell script could maintain these tests in a cross-platform maintainable way.
- Recommend a shell script for each manual test.
- Can someone write up a shell script that uses curl in order to do these manual tasks? Jared doing some test scripting now, Esme and others may assist.
- Beth: test scripts should be human readabale so that humans can execute these tests on their own. Adam: We still need a Test Compatibility Toolkit (TCK) to automate this no matter what. Still useful to have test cases target for humans to execute.
- Need JIRA tickets for test automation and to create a human readaable guide for manual testing by non-developers. (new JIRA Ticket:
)Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-1969 - Also need to run vagrant tests and consistency checks between Fedora, Solr and the triplestore.
- Test Camel messaging? Should test at least one camel message type.
Recent progress over the last three weeks
No comments
LDCX report-out
- Good presentations and discussions
- See links above in Agenda, items 3a-3f for detailed minutes for these sessions.
- 3a - Distributed repositories - shows value of Camel, messaging.
- 3b - Harmonizing Hydra and F4 AuthZ - encouraging.
- 3c - LDP Batch - may want to implement as extension module, until HTTP/2 is more widely adopted.
- HTTP/2 may be ready to be more widely adopted in 6-12 months.
- 3d - Cross repository modeling - encouraging.
Fedora Query interface
- Some people in the community, noted at LDCX and elsewhere, seem to want a query interface to Fedora. Others are not in favor of this idea as other components such as Solr are better suited to handle this.
- May be difficult to implement a query interface as the back-end stores underneath Fedora differ. Would not want to just re-use the Modeshape search API.
- Perhaps a general query interface based on messaging would work.
- Need to better identify whether the use cases for Fedora search are synchronous or asynchronous.
- Overall Message - how can we make it easier for people to implement an async query capability? Need to simplify this.
- Perhaps API-X would be a suitable location to host this functionality.