Bug 1757842
Summary: | Rebase to the latest Ruby 2.5 point release [rhscl-3] | |||
---|---|---|---|---|
Product: | Red Hat Software Collections | Reporter: | Vít Ondruch <vondruch> | |
Component: | ruby | Assignee: | Pavel Valena <pvalena> | |
Status: | CLOSED WONTFIX | QA Contact: | RHEL CS Apps Subsystem QE <rhel-cs-apps-subsystem-qe> | |
Severity: | unspecified | Docs Contact: | ||
Priority: | unspecified | |||
Version: | rh-ruby25 | CC: | djez, pvalena | |
Target Milestone: | --- | Keywords: | FutureFeature, Rebase, Reopened, Triaged, ZStream | |
Target Release: | 3.7 | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | rh-ruby25-ruby-2.5.9-9.el7 | Doc Type: | No Doc Update | |
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 1952998 (view as bug list) | Environment: | ||
Last Closed: | 2021-10-06 07:27:19 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: | 1784829, 1791293, 1796526, 1796785, 1831098, 1835860, 1886913, 1950523, 1952998 |
Description
Vít Ondruch
2019-10-02 14:31:48 UTC
(In reply to Vít Ondruch from comment #0) > https://www.ruby-lang.org/en/news/2019/10/01/ruby-2-6-5-released/ This is the correct link: https://www.ruby-lang.org/en/news/2019/10/01/ruby-2-5-7-released/ Ruby 2.5.8 is now available: https://www.ruby-lang.org/en/news/2020/03/31/ruby-2-5-8-released/ After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened. Ruby 2.5.9 is now available: https://www.ruby-lang.org/en/news/2021/04/05/ruby-2-5-9-released/ Moving to ON_QA for verification, because the z-stream errata was already released. After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened. |