RSpec Rails 6.0 Release Plan

[JonRowe]

@pirj @benoittgt we need to get some rspec-rails releases out, these are the steps we need to complete to do this:

• Merge / Cherry pick to 5-0-maintenance any outstanding 6.x patches we can
  • Support for Ruby 3.1 Add Ruby 3.1 for 5-0-maintenance #2564
• Release 5.0.3
• Create 5-1-maintenance without the Rails 7 patches.
• Merge / Cherry pick to 5-1-maintenance the final few tweaks for rails 6.1.
  • Support for Ruby 3.1 Setup 5-1-maintenance without Rails 7 but with Ruby 3.1 #2562
• Release 5.1.0
• Essential to merge to main
  • Support for Ruby 3.1 Add Ruby 3.1 (without Rails 7 support) to main #2563
  • Fix the type of handlers options passed to render #2521
  • Add Ruby 3.1 to CI and fix Rails 7 #2552
  • Sort out the mailer merges
  • Include ActiveSupport::Testing::TaggedLogging for Rails >= 7 (rebased) #2587
• Optionally
  • Release RSpec libs at 3.11
  • Merge to main Use RSpec.current_scope #2511 (see 3.11)
  • Merge to main Respect RSpec default_path for generators #2508
  • Merge to main Integration generator deprecation #2387
  • Merge Remove version-specific checks for unsupported Rails/Ruby #2614
• Merge Release prep for 6.0.0 #2567
• Release 6.0.0 supporting Rails 7, dropping Rails 5, minimum rspec version 3.11.

This is because major version changes are required for new rails versions for us under our release policy, but this means a bunch of branch wrangling, we could drop some of the changes for main in the name of expediency, thoughts?

[pirj]

we could drop some of the changes for main in the name of expediency

Sounds good.
I've restored the branch for #2546, those who want to have support for Rails 7 right now can use combo-have_enqueued_mail-fixes branch meanwhile.

[JonRowe]

I've restored the branch for #2546, those who want to have support for Rails 7 right now can use combo-have_enqueued_mail-fixes branch meanwhile.

Why? It's still merged in main. Only the new 5-1-maintenance skips it?

[pirj]

Because I've suggested using this branch 🙈 thinking that this commit will be taken out of main.

[JonRowe]

Please feel free to merge any rails 7 fixes to main as I intend to release this within a reasonable timeframe, if we were developing a longer term stable (like rspec 4) i'd revert but for rspec-rails its just as easy to pull the commits out of the stable 5.x series.

[pirj]

I'd prefer merging #2508 to main after releasing 5.1.x for simplicity.
Edited the description.

[pirj]

5-1-development is ready for 5.1.0 release, @JonRowe

[JonRowe]

I'm afraid its not @pirj, you merged my PR prematurely.

[JonRowe]

5.0.3 and 5.1.0 are released