Define Ruby Compatibility Policy

Hi there,

I think it'd be a good idea to define a compatibility/maintenance policy for the Ruby versions of rubycritic and I think that it should follow the Ruby core team's policy.

I don't see why our (considerably smaller) maintenance team should try to support versions that are not supported by the Ruby maintenance team.

Ruby 2.7 has been EOLed for almost one year now:

Source: https://www.ruby-lang.org/en/downloads/branches/

I think we should only maintain Rubies that are currently supported:

That would mean that right now we should only support:

• 3.0
• 3.1
• 3.2
• 3.3

The advantage of something like this is that we could use the latest version of our dependencies (e.g. reek) -- Right now people expect RubyCritic to work with Ruby 2.7 (e.g. https://github.com/whitesmith/rubycritic/issues/477) and I think that's an unrealistic expectation.

I'd like to know your thoughts on this (especially @nunosilva800)

Thanks,
Ernesto

Start by reviewing Ruby's supported branches page and the RubyCritic compatibility concern in issue #477. Resolve with maintainers which Ruby versions the project will support, then document the agreed policy and verify that the project's dependency expectations are consistent with it.