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

Tracking Issue to Release 0.7.4

Abierto
  • ¿Algo no está bien?
#369 2 comentarios 0 reacciones 1 asignado Ver en GitHub

Los mantenedores suelen responder en 1 día

@QwQBiG ya está trabajando en esto.

Desde el 14/10/2026.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

  • Release manager: @QwQBiG
  • Target version: 0.7.4
  • Previous release: 0.7.3 (v0.7.3)
  • Source cutoff: bd3efdfd55a36c62a739f993107780f4808afd07; defer #365 until after 0.7.4.
  • Release PR: #370 (merged).
  • Reviewed additions after the release PR: #371 (semaphore documentation) and #368 (blocking wait throughput).
  • Checked candidate commit: 3f521b528bcbe27cf632f1d35ff30dff9780ec3b.
  • Frozen release commit (RELEASE_COMMIT): pending.
  • Current phase / next action: complete the standard semver check and confirm the release commit.
  • Runbook: https://github.com/apache/asyncband/blob/bd3efdfd55a36c62a739f993107780f4808afd07/.agents/skills/release/SKILL.md

Prepare and freeze

  • Audit the selected source with license-audit; resolve release-blocking findings. All 268 tracked files were reviewed; no material licensing omissions were found.
  • Merge the version, lockfile, and undated changelog PR; review subsequent additions.
  • Confirm and record the frozen release commit.
  • Complete the final license review, including the actual Cargo package. All 93 packaged files were reviewed; no material licensing omissions were found.

Check the frozen release commit

  • cargo x lint
  • cargo x check
  • cargo x test --no-capture
  • RUSTUP_TOOLCHAIN=1.86.0 cargo x test --no-capture
  • cargo x semver --release-version 0.7.4
  • cargo publish --package asyncband --locked --dry-run from the clean checkout.
  • Required GitHub CI passes for the checked candidate: all 9 checks passed, including Miri and Required. https://github.com/apache/asyncband/actions/runs/38594955421.

Results for the checked candidate on 2026-10-15: stable Rust/Cargo 1.99.0 and Rust/Cargo 1.86.0 each passed 610 tests, with no failures or ignored tests; the online publish dry-run packaged and compiled 93 files without uploading. Audited crate SHA-256: 5d2050892d4691cf110586070786712b504985a4d37ed64a9cd8a402718e1706.

An offline comparison against the checksum-verified published 0.7.3 package passed 202 checks; 58 Minor rules were skipped under minor mode.

Candidate

  • RC / signed tag: pending
  • Compose run and attempt / package-check run: pending
  • ATR candidate URL / revision: pending
  • Source SHA-512: pending
  • Tag signer / source signer fingerprints and provenance: pending

Checklist:

  • Push the signed RC tag at the frozen commit; confirm both release workflows and ATR upload.
  • Download and verify the ATR revision: signatures, checksum, source contents against the RC commit, independent archive rebuild for automated signing, build, and packaging.
  • Complete the license review of the actual source archive and Cargo distribution; address ATR findings.

Vote and publish

  • ATR vote page: pending
  • PPMC vote thread: pending
  • PPMC result: pending
  • IPMC vote thread: pending
  • IPMC result: pending
  • Announcement: pending

Checklist:

  • Start the PPMC vote in ATR; record the vote link and closing time.
  • After the required duration and votes, resolve PPMC as Passed in ATR; record its result and the automatically started IPMC vote, and ensure that thread includes the PPMC tally link and any carried IPMC votes.
  • After the required duration and binding votes, resolve IPMC as Passed in ATR; record its result.
  • Confirm ATR publishes the voted revision to ASF distribution; record the SVN revision and download URL.
  • Push the signed final tag at the approved commit and approve/verify crates.io publication.
  • Verify ASF downloads and signatures, crates.io, and docs.rs.
  • Update the website Downloads page to this release and confirm it is live.
  • Send the announcement through ATR and record its archive link.
  • Merge the publication-date changelog PR and confirm superseded-release archival as applicable.
  • Close this issue after the preceding required items are complete.
Lenguaje dominante
Rust
Estrellas
283
Forks
49
Merge medio
1 d 9 h
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.