Bug #17508: io-console versioning

• Status: Closed
• Assignee: naruse (Yui NARUSE)
• Target version: -
• ruby -v: ruby 3.0.0p0 (2020-12-25 revision 95aff21468) [x86_64-linux]
• Backport: 2.5: DONTNEED, 2.6: DONTNEED, 2.7: DONTNEED, 3.0: DONE

[vo.x (Vit Ondruch)]

I have already complained about io-console versioning in #9591 but nothing really changed till today. There are ~15 commit atop of 2115a3937d0e2cf845d092aec1f6c25292ddd6ce, but the version was not bumped in Ruby 3.0. Does it really make sense to have independent versioning, when it does not provide the expected value?

[hsbt (Hiroshi SHIBATA)]

• Status changed from Open to Assigned
• Assignee set to nobu (Nobuyoshi Nakada)

[jeremyevans0 (Jeremy Evans)]

• Status changed from Assigned to Closed
• Assignee changed from nobu (Nobuyoshi Nakada) to naruse (Yui NARUSE)
• Backport changed from 2.5: UNKNOWN, 2.6: UNKNOWN, 2.7: UNKNOWN, 3.0: UNKNOWN to 2.5: DONTNEED, 2.6: DONTNEED, 2.7: DONTNEED, 3.0: REQUIRED

I created a pull request to backport the remaining changes in io-console 0.5.7 from master to the ruby_3_0 branch: https://github.com/ruby/ruby/pull/4252

[naruse (Yui NARUSE)]

• Backport changed from 2.5: DONTNEED, 2.6: DONTNEED, 2.7: DONTNEED, 3.0: REQUIRED to 2.5: DONTNEED, 2.6: DONTNEED, 2.7: DONTNEED, 3.0: DONE

ruby_3_0 b20e2c3f2a3ce227b9cf32d2bf02db0ac67eccb5.