Hiroshi SHIBATA
Hiroshi SHIBATA
@st0012 @mterada1228 If you found another issue about this PR, we can fix this in the future like RDoc 6.9.1 and Ruby 3.4.1.
It's an issue of https://github.com/rubygems/rubygems.org, not rubygems/rubygems that is client software.
How about https://github.com/jaredbeck/bundler-why?
I also agree to add the selectable options with SPDX identifier like `bundle gem --license=BSD-2-Clause`. But I'm against to add the specific option for Hippocratic License.
Can you separate tests of `fileutils` and `json`? and submit them to https://github.com/ruby/fileutils and https://github.com/ruby/json? It seems to work independently from this PR.
Thanks to file this. I'm re-working to develop the next major release from this week with https://github.com/rubygems/rubygems/pull/8887. This may be an issue caused by bumping the major version during the...
Can you separate isolate version constant and iterators and others?
We can change this with RubyGems 4.0. RG 3.0 has no incompatibility features. /cc @colby-swandale
My concern is "This is not only performance and usage feature; this is Ruby's philosophy about documentation." We shouldn't decide this change only one side.
RubyGems 4.0 is minimum requirements for this change. I'm going to ask matz, rdoc maintainers and other ruby core members about this change.