Add headius as committer

[headius]

Some of the recent releases of JRuby have been delayed for our users because the update of ruby-build took some time to merge. It would be more efficient if I could merge these changes myself. Pretty please? 🥺

JRuby 9.4.14.0 took about three hours: #2564

...but JRuby 10.0.2.0 took almost four days: #2558

Meanwhile, @eregon has commit rights, so TruffleRuby updates get merged almost immediately: #2570

The inconsistent merge delay has affected some of our production users when they are expecting to see JRuby releases available shortly after release. We push a ruby-build update as part of our release process, and I would like to also be able to merge those updates right away.

cc @mohamedhafez

[hsbt]

I'm +1 for you.

[mislav]

Agreed; that way we have committers from all major Ruby teams. 👍

[hsbt]

@mislav Can you add @headius to ruby-build team. I don't have maintainer role of that team.

[mislav]

@hsbt I've already invited them.

@headius The project is released using script/release in the scripts directory. It helps to have GitHub CLI installed. Homebrew bump is automatic after script/release tags a Release in this repository. While you're there, take a look at other scripts in the directory, such as update-eol! Thank you.

[hsbt]

I see, thanks!

[headius]

Invite has been accepted, thank you! Primarily, I just wanted to make sure my PRS were getting merged quickly, but if pushing releases along with that makes sense I'm happy to follow your procedure.

If that makes the most sense, I will incorporate that into my JRuby release tasks.

[mislav]

@headius You're welcome to script/release after merging your PRs, since that is equivalent to what @hsbt and @eregon do when there is a new release on their end.

Occasionally, it does happen that one maintainer cuts a release, but another maintainer merges another (unrelated) PR later that day and cuts another release because they were late for the first one. We don't have a backchannel where we communicate our intent around releases at all. Ideally, I would like to avoid having too many releases in a week, and maybe a way of accomplishing that would be to have some GitHub Actions automation that automatically releases in regular intervals if there is a new Ruby formula in the repository. That way maintainers could just merge & forget. But that's a discussion for a topic of its own.

[chadlwilson]

Thank you all for considering this! This will also shorten the lead time to get new jruby versions downstream into actions/setup-ruby as well, which is much appreciated.