Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Keep ATR email templates and announcement recipients in .asf.yaml

Abierto
  • ¿Algo no está bien?
#352 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
58/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
github, yaml
Área
release

Línea de trabajo

Start by reading .asf.yaml and the asfyaml schema entries for start_vote_subject, start_vote_template, announce_release_subject, announce_release_template, and announce_recipients under project.policy, then compare them with step 3 of the ATR guide. Define the vote and announcement templates and recipients in the project config, respecting the manual items listed in the issue. Done when ATR accepts the config and the release emails use the configured content and recipients.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Problem

During the 0.7.3 release (#327) I had to edit most of the generated emails by hand. ATR fills the vote and announcement emails from templates stored in its project settings, and the defaults don't fit our release well. The default vote email links the candidate page, the manifest, and KEYS and states the commit, but the checksums are only behind the manifest link, and it has no RC tag, signer fingerprints, changelog, or verification notes. ATR renders the Incubator round from the same stored template, so whatever I added by hand for the first round didn't carry over and I had to post it again as a reply on general@. The default announcement repeats "Apache" in the disclaimer, links the dist directory instead of the Downloads page, calls the release stable for production use, and its subject leaves out "Apache". The announcement recipients only include dev@, so [email protected] was added in CC by hand.

Proposal

As tison suggested in #338, the templates can live in .asf.yaml instead. The asfyaml project schema accepts start_vote_subject, start_vote_template, announce_release_subject, announce_release_template, and announce_recipients with CC under project.policy. ATR checks the variables each template uses when the config arrives, and we already have atr_sync on, so a change merged to main would be applied to ATR. Step 3 of the ATR guide could then shrink to what the templates can't fill in.

What stays manual

ATR has no template variable for the RC number, the RC tag, or the checksum, so the RC in the subject, the RC tag, and the verification notes stay with the release manager, although the manifest link already carries the checksums. I think a checksum variable would be easy to add upstream since ATR already computes them for the manifest, but the RC tag looks harder because ATR only knows its own revision numbers. The Incubator round also still needs a reply with the PPMC result and the carried votes. Separately, {{PODLING_DISCLAIMER}} renders "Apache Apache Asyncband" because it prefixes a project name that already starts with "Apache", so our template would write the disclaimer out until that's fixed in ATR.

Lenguaje dominante
Rust
Estrellas
274
Forks
42
Merge medio
1 d 35 min
PR fusionados (30 d)
39

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de apache/asyncband

Todos los issues de apache/asyncband

Issues similares

Más issues de Rust

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.