Issue #21804 has been updated by Eregon (Benoit Daloze). https://github.com/ruby/setup-ruby/pull/844 got merged the same day, what would you expect? Concretely I currently merge setup-ruby PRs and I have told @hsbt in the past he can merge (+ release) for new added versions. More people could be allowed, like release managers. So I think this is something to add to the post-release checklist: * Merge the ruby-build PR (e.g. https://github.com/rbenv/ruby-build/pull/2592) * Run this workflow: https://github.com/ruby/ruby-builder/actions/workflows/check-new-releases.ym... * Wait for the automated setup-ruby PR, CI and merge it * When RubyInstaller2 has a new release, run https://github.com/ruby/ruby-builder/actions/workflows/check-new-windows-ver... * Wait for the automated setup-ruby PR, CI and merge it ---------------------------------------- Misc #21804: Getting setup-ruby Earlier https://bugs.ruby-lang.org/issues/21804#change-115899 * 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/

Issue #21804 has been updated by mdalessio (Mike Dalessio).

https://github.com/ruby/setup-ruby/pull/844 got merged the same day, what would you expect?

A counter-example, though, is that the PR for windows support (https://github.com/ruby/setup-ruby/pull/847) took 3 days to get merged. I think @koic's original point is valid -- setup-ruby is an important foundational project depended upon by many (all?) downstream Ruby projects. A delay in releasing support in setup-ruby for new Rubies will cascade and multiply delays down the dependency chain in ways that are painful for other maintainers and users. In my case, because the Windows PR had not been merged, I was blocked from shipping Ruby-4-compatible native gems for sqlite3 and nokogiri. I eventually managed to ship these gems in a timely manner by forking setup-ruby and doing the work myself (see https://github.com/ruby/setup-ruby/pull/847). It wasn't _hard_ work, but it's work that's needlessly being imposed upon downstream maintainers. The community as a whole will benefit from faster turnaround time.

Maybe it'd make sense and possibly safe enough to automatically merge PRs by ruby-builder-bot, after they pass CI of course ... if someone is interested, please make a PR to setup-ruby.

I will take a look. ---------------------------------------- Misc #21804: Getting setup-ruby Earlier https://bugs.ruby-lang.org/issues/21804#change-115909 * 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/

Issue #21804 has been updated by Earlopain (Earlopain _). I don't really see the point of automerging PRs when someone still has to create the release manually. Merging the PRs is not much effort, someone just needs to do it. Having this happen as part of release management sounds reasonable to me. ---- But I think the bigger issue here is that windows builds are not first-party. So even if the release process gets adapted, issues like what @mdalessio wrote above will not be solved. Someone else handles the windows builds and that doesn't happen at the same time the release does, so there will always be some kind of delay (2 days this time I think, ignoring time to merge the PR) That said, for those that don't use windows in CI, changing something would still help. ---------------------------------------- Misc #21804: Getting setup-ruby Earlier https://bugs.ruby-lang.org/issues/21804#change-115918 * 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/

Issue #21804 has been updated by Eregon (Benoit Daloze). Eregon (Benoit Daloze) wrote in #note-2:

So I think this is something to add to the post-release checklist:

@hsbt Would you be willing to do those steps when releasing a new version? Is there a public release checklist somewhere? I think older releases are released by other release managers though, so we'd need them to do it too (and give them permission for it). ---------------------------------------- Misc #21804: Getting setup-ruby Earlier https://bugs.ruby-lang.org/issues/21804#change-115922 * 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/

Issue #21804 has been updated by p-linnane (Patrick Linnane). I left some thoughts in the PR, but will post here to keep discussion in one place.

Thanks for taking the time to open this PR to move the discussion forward, even though you’re understandably skeptical of the approach. I share your concerns.

For context, I’m a lead maintainer for Homebrew, where we make extensive use of automerging across our repositories, but only with significant guardrails. Our merge process is more complex than setup-ruby, but automerge is never fully hands-off. It only occurs after explicit human review and approval.

Given the critical role setup-ruby plays in the Ruby supply chain, I think a better path forward is increasing the number of people involved in release management, rather than further reducing human oversight. Adding release managers, as @eregon suggested on the bug tracker, seems like a safer and more sustainable solution.

Eregon (Benoit Daloze) wrote in #note-9:

I'd be OK with that, but it starts to be quite a few people and easy to forget, so currently I'm thinking the auto-merge + auto-release approach with appropriate guardrails is better and avoids adding even more work for Ruby releasers and myself, and I'm sure they are already very busy.

Would CODEOWNERS or a ping from the bot when a PR is opened not suffice for the 'easy to forget' portion? If the plan is to merge a PR, and then cut a release, this could be automated in GitHub Actions so that maintainers will only need to put eyes on a change, merge it, and be on their way. ---------------------------------------- Misc #21804: Getting setup-ruby Earlier https://bugs.ruby-lang.org/issues/21804#change-115924 * 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/

Issue #21804 has been updated by Eregon (Benoit Daloze). mdalessio (Mike Dalessio) wrote in #note-4:

A counter-example, though, is that the PR for windows support ([https://github.com/ruby/setup-ruby/pull/847](https://github.com/ruby/setup-ruby/pull/847)) took 3 days to get merged.

Windows got released on Dec 27 though, do you expect OSS maintainers to work through the winter holiday break to check PRs every day? (that's tricky, e.g. I'm typically abroad and without a computer at that period) I think one fundamental issue here is CRuby is doing feature releases at probably the worst time of the year. It would be fine if people don't have expectations of anything happening e.g. until the new year, but that's clearly not the case. ---------------------------------------- Misc #21804: Getting setup-ruby Earlier https://bugs.ruby-lang.org/issues/21804#change-116008 * 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/

Issue #21804 has been updated by larskanis (Lars Kanis). You can add me as a ruby-setup releaser, if that helps. I did some PRs already and know roughly how it works for Windows releases. But the RubyInstaller releases will not come out earlier. It's a project I care about, but it's still a spare time project. When a new ruby release comes out, I suddenly remember that there are several open issues, that the CI is broken and sometimes I notice some issues with the new release or other components. I'm not part of the ruby release process, so the RubyInstaller will always take a few days to follow. But I don't want to be part of the Ruby release process either, because my inability to do things in time would otherwise delay the release for all users. While I don't like requests with no reaction within half a year, everything within some days is OK for me. There is a mechanism to [force a particular commit before release](https://github.com/ruby/setup-ruby/pull/846#issuecomment-3694150617), which helps to overcome a pending release. That mechanism maybe could be described in the README. To be honest, I like the Christmas release date of Ruby. Over the holidays I can make all my open source projects compatible to the new ruby version and in the first week of January, I do the same at all the closed source code at work. Some co-workers wait urgent to work with the new release and others are telling me that my code doesn't run properly on RUBY-2.4! Yes really 2.4! ---------------------------------------- Misc #21804: Getting setup-ruby Earlier https://bugs.ruby-lang.org/issues/21804#change-116022 * 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/

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/