[ruby-core:102842] [Ruby master Bug#17508] io-console versioning
From:
naruse@...
Date:
2021-03-13 09:03:12 UTC
List:
ruby-core #102842
Issue #17508 has been updated by 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 commit:b20e2c3f2a3ce227b9cf32d2bf02db0ac67eccb5. ---------------------------------------- Bug #17508: io-console versioning https://bugs.ruby-lang.org/issues/17508#change-90900 * 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: DONE ---------------------------------------- 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:ruby-core-request@ruby-lang.org?subject=unsubscribe> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>