Release and dropping support of Ruby

[davidwessman]

Hello @glebm

1. Is it time to cut a new release?
2. Should we make a 1.2 release where we drop support for Ruby <3.1? (3.1 is EOL 2025-03-31)
3. If we create a Prism-parser to move away from the parser-gem, should we make it all backwards-compatible or should we add it as an alternative and then switch to it in a 2.0 release?
4. If we want to prepare for a 2.0 with breaking changes, is there anything else you have been thinking about?

Thank you! 🙂

[glebm]

v1.1 with dropped Ruby <3.1 support sounds good to me.
We should probably cut a release just before then.

I think eventually switching entirely to Prism in v2 makes the most sense.
There are probably custom extensions out there that derive from the parser-based scanners but hopefully they won't be too much work for users to migrate at their own pace.

I don't have anything else in mind in terms of breaking changes for v2.

[davidwessman]

@glebm will you release a v1.0* with the latest changes and then I'll start preparing for v1.1?

[glebm]

Released v1.0.15!