Issue #21804 has been updated by mdalessio (Mike Dalessio).
#844 got merged the same day, what would you expect?
A counter-example, though, is that the PR for windows support (#847) took 3 days to get merged.
... do you expect OSS maintainers to work through the winter holiday break to check PRs every day
Of course not. I can see that you're feeling attacked here, and that was not my intention, and I apologize. I'm thankful for all the work that you do. But the fact of the matter is that the setup-ruby project is critical path for much of the community, and the lack of a release holds up people who *are* working on open source over the holidays. I have no expectation that *you* *personally* should be responsible for cutting these releases at an inconvenient time. But since you're the maintainer of the repository, I do hope you would be involved to answer the question, "Should cutting a setup-ruby release be part of the ruby core release process?" and if the answer is yes, "How can that be done in a sustainable way?" I'm only getting involved here because I do tend to work on Ruby over the holidays, my projects depend on setup-ruby for proper testing, and I'm willing to help (as I've already tried to do in https://github.com/ruby/setup-ruby/pull/846 and https://github.com/ruby/setup-ruby/pull/847). ---------------------------------------- Misc #21804: Getting setup-ruby Earlier https://bugs.ruby-lang.org/issues/21804#change-116018 * Author: koic (Koichi ITO) * Status: Open ---------------------------------------- ruby/setup-ruby is commonly used for development in OSS projects and real-world Rails applications. https://github.com/ruby/setup-ruby This is not specific to Ruby 4.0.0. There is often a delay between a Ruby release and the availability of the corresponding version in setup-ruby. setup-ruby is maintained by the ruby organization and may take a few days to become available after a Ruby release. In contrast, ruby-build is maintained by the rbenv organization and tends to become available shortly after a Ruby release. This makes it easier to start using new Ruby versions immediately. If setup-ruby maintained by the ruby organization were released shortly after a Ruby release, users could start using new Ruby versions sooner. It is difficult to determine whether this issue should be registered on bugs.ruby-lang.org. Since setup-ruby is maintained by the ruby organization, this issue is being opened to raise awareness of the situation. If this is not appropriate, please feel free to close it. Thank you for your continued maintenance and for releasing Ruby. -- https://bugs.ruby-lang.org/