The future of ruby-loco

Offen
#972 2 Kommentare 1 Reaktion 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Anfängerfreundlichkeit
8/100
Issue-Typ
Feature
Klarheit
Muss geklärt werden
Aktivitätsstatus
Aktiv
Tech-Stack
github-actions, ruby
Bereich
devtools

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

  • 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

Vorherrschende Sprache
JavaScript
Sterne
1k
Forks
377
Ø Merge
4 T. 10 Std.
Gemergte PRs (30 T.)
13

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus ruby/setup-ruby

Alle Issues in ruby/setup-ruby

Ähnliche Issues

Weitere Issues zu JavaScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.