Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

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

Chiusa
  • Qualcosa non va?
#352 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
58/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
github, yaml
Ambito
release

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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.

Lingua principale
Rust
Stelle
277
Fork
44
Merge medio
1g 1h
PR unite (30g)
41

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di apache/asyncband

Tutte le issue di apache/asyncband

Issue simili

Altre issue su Rust

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.