Page Comparison

...

Meeting Logistics:

• Time: 9:00am PST PDT / Noon ESTEDT

• Zoom Meeting URL: https://princeton.zoom.us/j/7739591625
  (link will launch Zoom client – if you do not have Zoom, expand the instructions below)
  

...

Agenda (meeting notes below)

• Hyrax 4.0 Release Planning (Juliet Hardesty)

• (Please add agenda items)

Moderator: Heather Greer Klein

Notetaker: James Griffin

Attendees:

• Thomas Scherz

• Max Kadel (UNC Chapel Hill)

• Daniel Pierce

• Chris Colvard (Indiana University)

• Julie Hardesty

• Lynette Rayle

• Anna Headley

• (To be added)

...

Meeting Process

...

Notes

• 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

  (To be drafted)

  • • 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

    • With Valkyrized Hyrax, bugs and issues (which are also present in 3.x), should these be considered to be high priority issues for both?

      • Should we consider 3.x bugs and issues be high priority even with active releases for Valkyrized Hyrax?

    • Hyku was actively being upgraded from supporting Hyrax 2.x to Hyrax 3.x

    • Rails 7.0, Rails 6.1, Rails 6.0, Rails 5.2

      • Rails community has retained maintenance for Rails 5.2

      • https://guides.rubyonrails.org/maintenance_policy.html

    • Hyrax 2.x

      • No new commits from September 2021 onwards

    • Perhaps 4.0 will be the Rails upgrade and 5.0 shall be Valkyrized Hyrax?

      • Security updates will be needed still for 2.x

      • Rails and Ruby version timelines should be considered for security reasons

  • Resource Requests from the Community

    • May 7th is the next Partner Meeting

    • Partner Call is 11:30 EDT 2022-04-08, perhaps request the community resources needed to address the Rails/Blacklight upgrades

    • Checklist for Bootstrap and Blacklight upgrade items

      • It might be good to have this information accessible in preparation for the Partner Call (during which the resources would be requested)

      • Also, perhaps Daniel and Brad Watson (Emory) have some information regarding specific code changes which would need to be completed in order to support the upgrades

    • How can the resource request be prepared before the next Partner Call?

• Next Samvera Call

  • Notetaker

    • James

  • Moderator

    • Thomas Scherz

Call concluded at 09:29 PDT/12:29 EDT