...
Announcements
- Release Candidate
- State Tokens are missing: what do we want to do about it?
Remaining work
CTS
<your agenda item here>
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
5.0 Release
- Tickets
- Several tickets in review
- https://github.com/fcrepo/Fedora-API-Test-Suite/pull/260 - fairly large cleanup
- still an outstanding issue, not critical to the release. Jared assigned, to be completed by MondayJira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-1889
- Ben Pennell assigned, to be completed by MondayJira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2923 - Not all CTS tests passing yet
- not critical to the releaseJira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2784
- ready to go, just needs another committer to approveJira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2921
- needs reviewJira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2892 - CTS: If the spec says an implementation should return a certain response to indicate that an optional feature is unsupported, and such a response is recorded, the CTS should skip the test
- How do we feel about the release candidate?
- Andrew: we should take a day to do some sanity testing before release (candidate release testing page)
- Not doing a vagrant box for the RC
- UMD plan to do camel toolbox and 5.0 release testing and report any issues
- Java client: Decoupled from Camel toolbox but still useful for other purposes. Not a requirement for the release candidate
- Goal: release 5.0 by end of next week
- Do we have a release manager? Danny is willing. What is our goal for the RC? Community/ModeShape implementation plus the CTS.
- Alternate implementations are related for the release of the specification but not a requirement for the 5.0 release
- We should publish the HTML report of the CTS for 5.0, along with any from alternate implementations CTS doesn't currently report on the version of the software it is run against. It would be good to make this am optional user-provided parameterT