The future of ruby-loco
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 8/100
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,
ri2has 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
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from ruby/setup-ruby
-
Difficulty 1/5 Under an hour Newbie friendliness 20/100
ruby/setup-ruby#967 · 3 reactions ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
ruby/setup-ruby#801 · 3 comments ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 42/100
ruby/setup-ruby#791 · 3 comments ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
ruby/setup-ruby#752 · 12 comments ·
Maintainers usually reply within 1 day
-
mswin builds are missing bundle executable in BashMay be free again @MSP-Greg claimed this 761 days ago, and no pull request is open. Open
ruby/setup-ruby#658 · 4 comments · 1 assignee ·
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
manuXD270516/descanso#80 ·
Maintainers usually reply within 2 days
-
feat: Warn while typing a forbidden character in a file namePossibly taken @Mittalnew claimed this today. Openapp Drive 📁 enhancement OO Docs
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
linagora/twake-drive#4620 · 1 comment ·
Maintainers usually reply within 1 day
-
国战吕蒙【谋断】问题Open
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
Maintainers usually reply within 1 day
-
Edit: Hello TasteOpenchannels:edit check:passed
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
Maintainers usually reply within 1 day