The future of ruby-loco

Open
#972 2 comments 1 reaction 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
8/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active
Tech stack
github-actions, ruby
Domain
devtools

Research direction

This is a governance discussion about retiring ruby-loco builds in setup-ruby, not a code change to start from. Read the linked PRs #969 and #971 and the referenced bugs.ruby-lang.org issue 22180 for context. Done means the maintainers agree on a deprecation timeline and process, which a newcomer cannot decide alone.

Written by the indexing model from the issue text.

Description

  • For mingw based builds, it no longer makes sense to maintain support.
  • For mswin based builds, ruby org is going to provide official builds for both arm64 and x64, covering both releases and head.
  • For ucrt based builds, ri2 has already been consistently providing ruby-head builds for both arm64 and x64.

Given these conditions, I think it might be the time to retire the support of ruby-loco builds.

Now we have PRs like #969 and #971 already lined up, but before we proceed a bigger question is what would be the process of deprecating and/or removing support of ruby-loco. I'm opening this issue to start a discussion on what people want and what the process would look like.

There are a few considerations / questions:

  • @MSP-Greg: are you still committed to maintain ruby-loco long term, and do you want to keep the support in setup-ruby?
  • If we decided to commit the breaking change, we should probably have a deprecate warning period as discussed in the PRs. Is 1 month good?
  • Please add other topics as needed...

@eregon @MSP-Greg @larskanis @hsbt

Dominant language
JavaScript
Stars
1k
Forks
377
Avg merge
4d 10h
Merged PRs (30d)
13

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ruby/setup-ruby

All issues in ruby/setup-ruby

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.