[Feature Request] - Ruby 3.4

[toncid]

Is your feature request related to a problem? Please describe.

Extend the AL2023 DNF repo with Ruby 3.4.

Describe the solution you'd like

3.4 is the latest Ruby release available, whereas currently only 3.2 is supported out of the box.

There have been significant performance improvements added to the language in the last two versions.

Describe alternatives you've considered

Alternatives:

• Build from source via tools like rvm, rbenv or asdf.
• Use a 3rd-party Yum repo, like Fullstaq Ruby.

Additional context

This is a follow-up of #776, since Ruby has been updated in the meantime.

[jufemaiz]

Is this really that challenging for the AWS team?

[ozbenh]

Well, actually yes, properly namespacing ruby is fairly challenging and "just updating" would break some customers. You might notice that other enterprise distributions do not as a matter of fact update Ruby for the lifetime of their LTS (my Ubuntu LTS is at 3.2, afaik RHEL 9 is at 3.0).

That said, we do plan to provide a new versions before this one goes EOL

[jufemaiz]

Well, actually yes, properly namespacing ruby is fairly challenging and "just updating" would break some customers. You might notice that other enterprise distributions do not as a matter of fact update Ruby for the lifetime of their LTS (my Ubuntu LTS is at 3.2, afaik RHEL 9 is at 3.0).

That said, we do plan to provide a new versions before this one goes EOL

The default I understand, but ensuring that current release is available via the official YUM repo would be adviseable.

That latter is the critical part.

We saw how long it took for a Ruby3.x release on Lambda (after the Ruby2.7 had been officially EOL'd).

[phene]

It's already available for ElasticBeanstalk on AL2023, so what's the hold up here? I usually expect ElasticBeanstalk to be trailing in terms of updates rather than leading.

[gnuheidix]

@stewartsmith It would be awesome to get a statement whether we will get a new version packaged prior to the scheduled EOL of Ruby 3.2 in AL2023 or not. Clear statements are important for the user-base especially in this case because workarounds are not trivial.