Bug 1757842 - Rebase to the latest Ruby 2.5 point release [rhscl-3]
Summary: Rebase to the latest Ruby 2.5 point release [rhscl-3]
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Software Collections
Classification: Red Hat
Component: ruby
Version: rh-ruby25
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 3.7
Assignee: Pavel Valena
QA Contact: RHEL CS Apps Subsystem QE
URL:
Whiteboard:
Depends On:
Blocks: 1784829 1791293 1796526 1796785 1831098 1835860 1886913 1950523 1952998
TreeView+ depends on / blocked
 
Reported: 2019-10-02 14:31 UTC by Vít Ondruch
Modified: 2021-10-06 07:27 UTC (History)
2 users (show)

Fixed In Version: rh-ruby25-ruby-2.5.9-9.el7
Doc Type: No Doc Update
Doc Text:
Clone Of:
: 1952998 (view as bug list)
Environment:
Last Closed: 2021-10-06 07:27:19 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Vít Ondruch 2019-10-02 14:31:48 UTC 
Ruby 2.5.7 is now available:

https://www.ruby-lang.org/en/news/2019/10/01/ruby-2-6-5-released/
Comment 2 Vít Ondruch 2019-10-02 14:33:59 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/
Comment 4 Vít Ondruch 2020-08-24 14:00:55 UTC 
Ruby 2.5.8 is now available:

https://www.ruby-lang.org/en/news/2020/03/31/ruby-2-5-8-released/
Comment 7 RHEL Program Management 2021-04-05 13:42:44 UTC 
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.
Comment 8 Vít Ondruch 2021-04-06 10:13:42 UTC 
Ruby 2.5.9 is now available:

https://www.ruby-lang.org/en/news/2021/04/05/ruby-2-5-9-released/
Comment 14 Vít Ondruch 2021-05-26 14:39:35 UTC 
Moving to ON_QA for verification, because the z-stream errata was already released.
Comment 16 RHEL Program Management 2021-10-06 07:27:19 UTC 
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.
Note You need to log in before you can comment on or make changes to this bug.