Jon Rowe
Jon Rowe
The next major version will do so.
From RSpec 4, we will be adopted more of a "breakver" style of support for Ruby, every minor point release will support the "at time of first release supported Ruby...
There is not enough bandwidth amongst the team to add another Ruby to the supported set. Unlike Rails we are a small team without the backing of any companies. So...
To clarify my comments from the original rspec-core pr, #2942, I'd actually be ok with having a seperate CI build on our repos that runs cron and on branches with...
We do already have a seperate proof of concept repo for this, theres a lot to do to make this happen, we need to think about builds (multiple), how we...
Honestly I think what is needed is a script that does the relevant repo merging that can be reviewed, and used on a sample repo so we can peruse the...
So I've created a branch called setup on https://github.com/rspec/rspec-monorepo-prototype which contains this script and have run it to create `master-20200503` Some thoughts I have so far are that, we are...
Its more that we have commits which reference the pull request number, which would not exist in the new repo, but the old repos will continue to exist, we'll just...
This is how rails handles it https://github.com/rails/rails/releases They just release all versions in lock step, maybe thats easier, we could adopt that from rspec 4