The future of ruby-loco

Ouverte
#972 2 commentaires 1 réaction 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
8/100
Type d'issue
Fonctionnalité
Clarté
À clarifier
Activité
Active
Stack technique
github-actions, ruby
Domaine
devtools

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

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

Langage dominant
JavaScript
Étoiles
1k
Forks
377
Merge moyen
4 j 10 h
PR mergées (30 j)
13

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de ruby/setup-ruby

Toutes les issues de ruby/setup-ruby

Issues similaires

Plus d'issues JavaScript

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.