...
Fixing bugs as they come up on the mailing list...
- Andrew Woods advocates ownership, implying need for SG to create space for employees to do this work
- A. Soroka observes that this raises sustainability issues if core committers are obligated to non-kernel/api issues, especially fcrepo-ext
- Esmé Cowles notes that approachability of the stack affected determines speed of issue address
- FCREPO-1980 being investigated by Unknown User (acoburn)
- 4.5.1 RC-2 testing status
- Hydra testing outstanding, Esmé Cowles will look into it
- Release Testing Procedures - Template for future release.
- Should we automate test environments eg, with leveldb, with postgres, etc., maybe on travis CI?
Fedora Specification
- Messaging SPI <- close to done, need to tighten RDF serializations
- Atomic Batch Operations
- CRUD <- needs to include elements of RESTful HTTP API
- Resource Versioning <- not currently aligned with reference F4 impl, since that is just a copy/exposure of JCR which cannot be imported into specs
- Binary Fixity Checking <- needs help
- Authorization <- needs help
- Benjamin Armintor will bug Rob Sanderson about a couple of issues in Versioning and CRUD/Asynch
Should we remove old release candidates from github? https://github.com/fcrepo4/fcrepo4/releases
Yes.
Looking for a Fedora techie to attend Archivematicamp
Can anyone attend? There's an integration workshop! It's funded! Maybe Alan.
With scripts as a starting point, TCKs in Ruby?
- Should
be closed?Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-1692 - Should Yinlin Chen continue working on https://github.com/yinlinchen/fcrepo4-release-tests ?
- Should
- A complementary service to fcrepo-serialization?
- ...
Status of "in-flight" tickets
Expand Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 40 jqlQuery filter=13202 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5
...