Time/Place
This meeting is a hybrid teleconference and IRC chat. Anyone is welcome to join...here's the info:
- Time: 11:00am Eastern Daylight Time US (UTC-4)
- Dial-in Number: (712) 775-7035
- Participant Code: 479307#
- International numbers: Conference Call Information
- Web Access: https://www.freeconferencecallhd.com/wp-content/themes/responsive/flashphone/flash-phone.php
- IRC:
- Join the #fcrepo chat room via Freenode Web IRC (enter a unique nick)
- Or point your IRC client to #fcrepo on irc.freenode.net
Attendees
- A. Soroka
- Jared Whiklo
- Danny Bernstein
- Esmé Cowles
- Katherine Lynch
- Marcus Barnes
- Nat Kanthan
- Daniel Lamb
- Michael Durbin
- Jim Coble
- Yinlin Chen
- Youn Noh
- Bethany Seeger
- David Wilcox
- Frank Smutniak
- Aaron Coburn
- Jonathan Green
- Joe Harrington
Agenda
- 4.7.0 release candidate - testing and migration
- Backup/Restore issues
- 4.6.1 release - patch for concurrent resource creation
- Semantic versioning, API Specifications and releases post-4.7.0
- new fcrepo-vocabulary repository?
- API Specification - Taking it to the streets
- Move Yinlin's tests into fcrepo4-labs
Status of "in-flight" tickets
Ticket Summaries
Please squash a bug!
Tickets resolved this week:
Tickets created this week:
Minutes
Status of release testing:
- The process seems to be going well.
- ActiveFedora issue does not seem to be a blocker. Ideally Drew can provide feedback before we turn the crank.
- Danny Bernstein will rerun steps that seemed to be broken.
- Release schedule: Halloween? Let's plan for early-ish on Monday after talking to Drew and Stephano.
- Jared Whiklo is concerned that we haven't the data migration enough - will touch base with Drew
- Andrew Woods will circle up with Stephano and the gang about migration
- Andrew Woods will check with Drew that all is well with Michael Durbin's 4.6.1 patch before dropping the monkey.
Semantic versioning, API Specifications and releases post-4.7.0
The community wants semantic versioning.
But the community wants no more than one major release per year, minor releases as necessary.
There are two factors that define a major release:
- breaking changes to the API
- required backend data migration
Ideally we would finish the API work before the next major release (5.x).
Should we strive for this? Yes: there is a consensus on the call.
Do we think that we'll need more near term releases with breaking changes at the REST API level before we get to 5.x?
Is 6-8 months enough time to solidify the REST API and align the implementation with it?
- A robust test suite should be part of that alignment.