...
Noah: https://www.ruby-lang.org/en/news/2013/12/21/ruby-version-policy-changes-with-2-1-0/
Trey: The major release number is more for branding, but there are API incompatible changes in minor releases for Ruby
Definitely going to test 2.4, as possible test for 2.5 and 2.6
Matrix complexity for two Rails versions becomes burdensome
Mark: If we put 2.6 in, and find that it breaks tests, then delegate it to this WG
Bess: But we should put 2.6 into the test matrix
Trey: Concerned about adding 2.6 to test matrix, it does slow the builds, but we should add it if it does not break tests
Tom: CircleCI with 4 builds running parallelized with 4 containers will provide 16 container environments
Trey: We agreed upon three most recent versions of Ruby
Mark: Articulate what we test vs. what we guarantee for stability
At various points, there will be pressure to introduce support for a newer release of Ruby
Noah: We can't necessarily issue a guarantee this once a Ruby release is issued at the end of the year
Trey: This seems more like a documentation problem, we can document the cases where the three latest Ruby versions cannot be supported