Skip to content

Commit 0fc657d

Browse files
committed
Document the role of the setup-ruby release team and maintainers
1 parent 9fd324a commit 0fc657d

File tree

1 file changed

+20
-2
lines changed

1 file changed

+20
-2
lines changed

CONTRIBUTING.md

Lines changed: 20 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -25,6 +25,24 @@ $ cp pre-commit .git/hooks/pre-commit
2525
This is entirely automated now since [this issue](https://github.com/ruby/setup-ruby/issues/254).
2626
If you do not see a new version more than 24 hours after it was released feel free to file an issue.
2727

28-
## Release
28+
## Release team
2929

30-
Maintainers can create a release automatically by running [this workflow](https://github.com/ruby/setup-ruby/actions/workflows/release.yml).
30+
The current release team is @eregon @MSP-Greg @ntkme @flavorjones @larskanis @headius.
31+
They all have write access to the `setup-ruby` repository, to be able to merge and release `ruby-builder-bot` PRs adding new versions.
32+
The `ruby-builder-bot` PRs are created by [this workflow](https://github.com/ruby/ruby-builder/actions/workflows/check-new-releases.yml) which runs every hour.
33+
34+
The release team can create releases by running [this workflow](https://github.com/ruby/setup-ruby/actions/workflows/release.yml).
35+
36+
The release team and more specifically @larskanis can run [the workflow to check for new RubyInstaller releases](https://github.com/ruby/setup-ruby/actions/workflows/check-new-windows-versions.yml) to speed things up (otherwise it's run twice a day).
37+
38+
The release team must not merge other PRs than the ones from `ruby-builder-bot` (unless they are also setup-ruby maintainers).
39+
40+
## Maintainers
41+
42+
@eregon is the lead maintainer and creator of this action.
43+
Any design change (e.g. new input, different way to do things) must have his approval.
44+
45+
@MSP-Greg @ntkme are maintainers of setup-ruby and should feel free to merge bug fixes, etc.
46+
They should request a review on their PR from another maintainer but they don't have to wait for the review if the fix is urgent (e.g. `setup-ruby` broke in some cases and the fix is obvious).
47+
48+
Naturally maintainers can also [release setup-ruby](https://github.com/ruby/setup-ruby/actions/workflows/release.yml) so the changes from their PR get published.

0 commit comments

Comments
 (0)