Drop old version support?

[jdelStrother]

I wanted to add a small feature, but before I do wondered if we should try & tidy up some of the legacy code. Shall I create a PR that drops EOL Rubies & Rails, or do you already have something in progress?

The readme says

Forthcoming flag_shih_tzu v1.0 will only support Ruby 2.2+, JRuby-9.1+ and Rails 4.2+

I'm guessing that's a little out of date..?

Rails 7.1 becomes EOL on 1st October 2025. We could only support >= 7.2 , though it wouldn't be a bit deal to allow, eg, >= 7.0 if we really wanted.

Ruby 3.1 became EOL on 31st March 2025. Maybe we only support >= 3.2 ?

I know very little about jruby, but it sounds like we should only support >= 9.4 at most.

[pboling]

💯 This is on my list of things to do! It would be a major version bump, and I wanted to cleanup the code and do another release before doing the major bump.
But, absolutely dropping older versions of Ruby and Rails is the plan.
I think Rails >= 7.0 is a fine target.
Once the code is cleaned up a bit, we could do two major releases in quick succession.

Once for this:

Forthcoming flag_shih_tzu v1.0 will only support Ruby 2.2+, JRuby-9.1+ and Rails 4.2+

And then again for this (maybe a v2.0):

Rails >= 7.0

I have been putting a huge amount of effort into preparing my gem templating tool, kettle-dev, which I will be using to apply a noramtive template here soon.

Also - we have a Discord now if you want to live chat about it:

Also, I'm setting up an open source collective for all the projects in this org (50+):