...
Trey: hydra-head would be useful due to its complexity
(All agreed with this as the candidate)
Trey volunteered to exploring this, along with Noah
Need to test the versions of Ruby and Rails which we've agreed to test
Which have we agreed to test?
Tom: For Hyrax, there is a policy for dropping deprecated Ruby versions
When a Hyrax major release comes out, unsupported Ruby versions on that date are dropped
Whenever they can, update the support for the latest Ruby releases
Trey: Guidelines state that it is up to the product owner
Should we revisit that?
Noah: This WG has the opportunity to provide some guidance given that the Product Owners may be more focused elsewhere
Trey: Are we supporting Ruby versions under normal maintenance (not security maintenance) or just not EOL?
Tom: We support Ruby versions which are just not EOL
Trey: Which Ruby versions easily installed on operating systems (such as Ubuntu) using package managers
Noah: If it is practical to align with Ruby community calendars, then we should aim for this
Trey: We are not supporting 2.2
2.3 will be EOL'd before this WG concludes this phase
Proposes that we only support Ruby releases under normal maintenance)
Mark: End of this month is the end of support for 2.3
Tom: Assuming that Hyrax 3.0.0 is released before this date, we would drop support
Trey: Each EOL for a Ruby release should trigger a Gem release for components
We will support the last three Ruby versions
See if this is reasonable, we might not support 2.6
Bess: We want to be testing against 2.6
Trey: Yes, 2.6, 2.5, 2.4