Time/Place
This meeting is a hybrid teleconference and slack chat. Anyone is welcome to join...here's the info:
- Time: 11:00am Eastern Daylight Time US (UTC-4)
- Audio/Video Conference Link: https://duraspace.zoom.us/my/fedora
Dial-in:
+1 408 638 0968
+1 646 876 9923
+1 669 900 6833
Meeting ID:
812 835 3771
Join fedora-project.slack.com on the "tech" channel
Attendees
- Danny Bernstein
- Peter Eichman
- Bethany Seeger
- Jared Whiklo
- Andrew Woods
- Ben Pennell
- Aaron Birkland
- Mohamed Mohideen Abdul Rasheed
- David Wilcox
- James Silas Creel
- Jon Roby
Agenda
Announcements
- Sprint 2
- Are we ready to release RC 1?
Remaining work
CTS
- Are we ready to release RC 1?
<your agenda item here>
Please squash a bug!
Tickets resolved this week:
Tickets created this week:
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 Monday
- - Ben Pennell assigned, to be completed by Monday
- Not all CTS tests passing yet
- - not critical to the release
- - ready to go, just needs another committer to approve
- - needs review
- 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 parameter