Cleaning house with RSpec Rails 4
summary
Clear concrete announcement: RSpec Rails 4 versions separately aligned with Rails majors, so majors follow Rails releases and minors follow Rails minors. CI and supported matrix change: drops support for Rails <5.0 and Ruby <2.3 (with a one-time 4.2 CI pass), JRuby regains CI support, and a beta gem exists now. Most changes are build and dependency pruning rather than production code. Call for contributors to triage and fix piling bugs and add Rails feature support.
AI-written summary · about
chapters (21)
- 0:00Intro
- 0:18CLOUD Pain Free Rails 66 Deployments
- 2:13Compatibility
- 3:49bundle update
- 5:44Installing nokogiri 1.10.3 with native extensions
- 7:00What does "breaking" mean?
- 7:11The SemVer spec doesn't define breaking change
- 7:34THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE
- 10:36Breaking changes cannot be defined on a purely source code basis
- 12:00SemVer is a mechanism for communicating intent
- 13:25Versioning strategy
- 14:46Rails specific code
- 15:53No need for an RSpec major
- 18:03Consensus on strategy change
- 18:57Take RSpec Rails off RSpec versioning
- 19:13Major, removing support for any newly unsupported versions of Rails, and adding support for the new major.
- 19:30Minor, adding support for the new features Additionally, release minors for any new RSpec features
- 19:45Every library should cleanly define breaking change
- 20:53Wait for Rails 6.0 release candidate
- 24:45RSpec Rails needs your help
- 24:56Only keeping core Rails features supported
