...
Time: 9:00am PDT / Noon EDT
Zoom Meeting URL: https://princeton.zoom.us/j/7739591625
(link will launch Zoom client – if you do not have Zoom, expand the instructions below)
...
Hyrax 4.0 Release Planning
We are not ready for 4.0
Previously, community maintained 3.x and maintaining 2.x
Now with Valkyrie, 4.x releases need to be supported along with the ActiveFedora Hyrax for 3.x
Will 4.0 need to come sooner with Rails 6/Blacklight upgrades? These would introduce breaking changes
Valkyrie may need to, then, become a later release
If this is the case, Rails 6/Blacklight would need to be a higher priority
Perhaps this can be prioritized for the Dev Congress?
Currently, this work is ongoing, but we do not know where the community will arrive during May
Do we have a sense of what proportion of the community are still on 2.x, and what their path to upgrade is looking like?
At a minimum, Hyku may still lock adopters to 2.x releases
Max is aware of implementations which currently use 2.x releases
How can Samvera support smaller or less-resources institutions in upgrading to a more recently-released, supported version?
When was 3.x released?
Approximately one year ago
During the past, 2.x releases were motivated by those institutions which required these updates for their own custom implementations
Might it be possible to propose a timeline for ending support for 2.x releases following the 4.0 release?
Do we have a set of standardized practices regarding the length of support for each major/minor release series?
We do not, but it is suspected that we implicitly promise that the test suite will continue to pass for 2.x release branches
James needs to ensure that CircleCI nightly test suites are running for main branches for samvera components and samvera-labs projects