...
- Now that the release candidate is out, let's focus on testing.
- Yin will try vagrant today and verify whether or not it is broken.
- try "vagrant box update"
- Possible to tie vagrant to a specific version of the base box? Since base boxes can shift under a fedora version and cause confusion...
- Nick Ruest will look into this.
- Who will help with testing?
- Danny
- Nick
- Aaron Birkland
- Some focus should be brought to migration of existing repositories
- Who might be willing to attempt such a migration test?
- ?
- Jared: Please test something
- Yin will try vagrant today and verify whether or not it is broken.
- LDP Test Suite: We need to maintain this thing - at least insofar as the tool should still run:
- We should come to an agreement with Rob and others about the terms of maintenance.
- Do we fork this project ?
- Project still runs, but will break. Maintainers are not responding.
- Chris Beer has identified a problem with the Test Suite and has a pull request in.
- A. Soroka will open a JIRA to track this issue. (
)Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2249 - Andrew Woods will move this onto the agenda of LDP Next
- HydraConnect:
- Anyone up for a meetup?
- Who will be there:
- Esme, Kate, Yinlin, Ben, Andrew Woods, Bethany
- Any ideas of how to use this opportunity?
- Containerizing in Production Deployment
- Import/Export unconference session? Yes - there is interest there
- Informal get together? Yes there is interest.
- Lunch Wednesday or Thursday?
- Bethany Seeger will organize.
- Lunch Wednesday or Thursday?
- It is not always clear which versions of which pluggable components are compatible with which version of fcrepo4.
- Andrew Woods surfaced the need to maintain a compatibility matrix or at least capture this information somewhere in the documentation.
- Proposal: When a component is released, document which fcrepo4 version it will work against, whether in a compatibility matrix or in the readme.
- General agreement: any release notes should note which fcrepo4 the component was tested against.
- Andrew Woods : Add a note to EXTS policy docs indicating that people must document which version of fedora was used with integration tests (where applicable)
- Andrew Woods surfaced the need to maintain a compatibility matrix or at least capture this information somewhere in the documentation.
- Next week Andrew Woods will be gone: Any high priority work / blockers that should be raised? No.
- Comments on the API dependencies:
- Who will tackle each component:
- Resource CRUD:
- A. Soroka will reach out to Ben, Tom Johnson, Danny Lamb
- Resource CRUD:
- Who will tackle each component:
...