The future of ruby-loco

Aberta
#972 2 comentários 1 reação 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
5/5
Tempo estimado
Mais de uma semana
Facilidade para iniciantes
8/100
Tipo de issue
Funcionalidade
Clareza
Precisa de esclarecimento
Status de atividade
Ativa
Stack de tecnologia
github-actions, ruby
Domínio
devtools

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

  • 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

Linguagem predominante
JavaScript
Estrelas
1k
Forks
377
Merge médio
4d 10h
PRs com merge (30d)
13

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de ruby/setup-ruby

Todas as issues de ruby/setup-ruby

Issues semelhantes

Mais issues de JavaScript

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.