Issue #21804 has been updated by naruse (Yui NARUSE). Releasing a new Ruby version around Christmas is certainly done with some intention in mind — it's nice to let people who enjoy OSS during the holidays try out the latest Ruby right away and have some fun with it. So I do understand the desire to get setup-ruby updates to everyone quickly. That said, Ruby releases are work that quite a few people in the past have found really challenging and eventually stepped away from. When I took it on, my guiding principle has been to keep the ongoing, routine tasks as sustainable and low-stress as possible. For that reason, I'd really prefer not to add any new steps to the process even something that seems as straightforward as just pressing one button. Also, I don't want to make people who prefer to spend Christmas on non-OSS things feel pressured to work on it. With these kinds of constraints in mind, improving the process becomes quite a technical and thoughtful challenge. I agree that we should discuss about "How can that be done in a sustainable way?" I'd really appreciate it if koic-san, who opened this ticket, could also consider it from this perspective. ---------------------------------------- Misc #21804: Getting setup-ruby Earlier https://bugs.ruby-lang.org/issues/21804#change-116183 * 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/