[ruby-core:102793] [Ruby master Bug#17508] io-console versioning

Issue #17508 has been updated by jeremyevans0 (Jeremy Evans).

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
Assignee changed from nobu (Nobuyoshi Nakada) to naruse (Yui NARUSE)
Status changed from Assigned to Closed

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

----------------------------------------
Bug #17508: io-console versioning
https://bugs.ruby-lang.org/issues/17508#change-90815

* Author: vo.x (Vit Ondruch)
* Status: Closed
* Priority: Normal
* Assignee: naruse (Yui NARUSE)
* 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: REQUIRED
----------------------------------------
I have already complained about io-console versioning in #9591 but nothing really changed till today. There are ~15 commit atop of commit: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?



-- 
https://bugs.ruby-lang.org/

Unsubscribe: <mailto:[e-mail]?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>