Bug 1938942
Summary: | Release ruby 3.0 for RHEL 8 | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 8 | Reporter: | Grzegorz Grasza <ggrasza> |
Component: | ruby | Assignee: | Jarek Prokop <jprokop> |
Status: | CLOSED ERRATA | QA Contact: | Dita Stehlikova <dstehlik> |
Severity: | medium | Docs Contact: | Lenka Špačková <lkuprova> |
Priority: | unspecified | ||
Version: | 8.3 | CC: | annelson, dstehlik, jhouska, jkejda, jprokop, vondruch |
Target Milestone: | rc | Keywords: | Triaged |
Target Release: | --- | Flags: | pm-rhel:
mirror+
|
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | ruby-3.0-8050020210730101334.b4937e53 | Doc Type: | Enhancement |
Doc Text: |
.A new module stream: `ruby:3.0`
RHEL 8.5 introduces `Ruby 3.0.2` in a new `ruby:3.0` module stream. This version provides a number of performance improvements, bug and security fixes, and new features over `Ruby 2.7` distributed with RHEL 8.3.
Notable enhancements include:
* Concurrency and parallelism features:
** `Ractor`, an Actor-model abstraction that provides thread-safe parallel execution, is provided as an experimental feature.
** `Fiber Scheduler` has been introduced as an experimental feature. `Fiber Scheduler` intercepts blocking operations, which enables light-weight concurrency without changing existing code.
* Static analysis features:
** The `RBS` language has been introduced, which describes the structure of `Ruby` programs. The `rbs` gem has been added to parse type definitions written in `RBS`.
** The `TypeProf` utility has been introduced, which is a type analysis tool for `Ruby` code.
* Pattern matching with the `case/in` expression is no longer experimental.
* One-line pattern matching, which is an experimental feature, has been redesigned.
* Find pattern has been added as an experimental feature.
The following performance improvements have been implemented:
* Pasting long code to the `Interactive Ruby Shell (IRB)` is now significantly faster.
* The `measure` command has been added to `IRB` for time measurement.
Other notable changes include:
* Keyword arguments have been separated from other arguments.
* The default directory for user-installed gems is now `$HOME/.local/share/gem/` unless the `$HOME/.gem/` directory is already present.
To install the `ruby:3.0` module stream, use:
[literal]
----
# yum module install ruby:3.0
----
If you want to upgrade from an earlier `ruby` module stream, see link:https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html-single/installing_managing_and_removing_user-space_components/index#switching-to-a-later-stream_managing-versions-of-appstream-content[Switching to a later stream].
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2021-11-09 18:48:13 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 1969483 |
Description
Grzegorz Grasza
2021-03-15 09:58:02 UTC
#1916404 needs this patch: https://github.com/ruby/ruby/commit/04b5203a031d372b725e407519f10da6deda0e78#diff-73ed31bea018f3a994e757faebca1dbf4edb3027ca4a1ecdd623abc955b8e2f6 Just to clarify, we can provide Ruby 3.0 in RHEL8, not in CentOS and that is something we are considering. If there was Ruby 3.0 available in RHEL8, it would be available as new stream of ruby module. Also, if you are interested in the specific issue you have referenced in comment 2, that is something which can be considered for backport into older Ruby releases. But that would probably deserve separate ticket. (In reply to Vít Ondruch from comment #4) > Just to clarify, we can provide Ruby 3.0 in RHEL8, not in CentOS and that is > something we are considering. If there was Ruby 3.0 available in RHEL8, it > would be available as new stream of ruby module. We are primarily concerned with RHEL8, I put Centos8 in the title only because I looked at other bugs on the ruby component and wanted to make it consistent, so I'll change the title of this bug to reflect that fact. > > Also, if you are interested in the specific issue you have referenced in > comment 2, that is something which can be considered for backport into older > Ruby releases. But that would probably deserve separate ticket. We will be satisfied with either Ruby 3.0 or a backport of this change, so I would like to defer the decision to you, whichever makes more sense from your perspective. (In reply to Grzegorz Grasza from comment #5) > > Also, if you are interested in the specific issue you have referenced in > > comment 2, that is something which can be considered for backport into older > > Ruby releases. But that would probably deserve separate ticket. > > We will be satisfied with either Ruby 3.0 or a backport of this change, so I > would like to defer the decision to you, whichever makes more sense from > your perspective. Would you mind filing separate ticket with this request and some justification why is this important and what specific issue this solves? Thx a lot. Ack, I added a new bug specifically about this one issue here: https://bugzilla.redhat.com/show_bug.cgi?id=1944227 VERIFIED ruby:3.0 is available version: ruby-3.0-8050020210730101334.b4937e53 <-> https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=1680927 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (new module: ruby:3.0), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2021:4282 |