RFC: versioning strategy

[fables-tales]

view rendered

Please leave comments on the PR. The render link will update as new commits get pushed.

[myronmarston]

👍

For the purposes of this versioning strategy, we consider removing a Rails or Ruby version to be a breaking change.

It's worth calling out that we're discussing changing this for RSpec (see rspec/rspec#25). Not sure what affect (if any) that should have on rspec-rails, though.

[JonRowe]

I entirely support this, my only comment is how will rspec-rails handle major releases of RSpec going forward, and what affect if any RSpec dropping ruby version support (as discussing in rspec/rspec#25) have on this? (I think none as Rails only supports in life Ruby?)

[fables-tales]

This depends on the details of how RSpec majors get released, the intent is to move RSpec Rails to public API of RSpec, so I suspect when RSpec goes through a major that actually affects the API, we'll need to support both versions. This will be a good test to make sure our plugin api is powerful enough to actually support an extension of the magnitude of RSpec Rails.

[BobbyMcWho]

LGTM

[fables-tales]

I think we can consider this accepted. Merging.