T27-06 — Baseline: run the four dist builds and record sizes and digests

Aperta
  • Qualcosa non va?
#42 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
35/100
Tipo di issue
Funzionalità
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
rust
Ambito
build-system, release

Direzione di ricerca

Start with xtask/src/dist.rs and the T27-06 ledger at docs/tasks/T27-06-dist-build-baselines.md; check which dist options are available on the current branch. Run the four commands listed in the issue where supported, recording each artifact's path, size, and SHA-256, and note the cause of any command that cannot run. Done when a dated receipt records all artifacts and blockers.

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

Descrizione

ci release

T27 row: T27-06
Work package: RP-00 — Inventory, release contract, baseline, task ledger
Priority: P0
Status: IN PROGRESS

Objective

Run dist --native, dist --web, dist --source and dist --sbom on the release candidate and record the size and SHA-256 of everything produced, so later rows compare against a known starting point rather than against nothing.

Acceptance criteria: All four dist commands run; every produced artifact has a recorded size and SHA-256; failures are recorded with their cause.

Inputs

xtask/src/dist.rs; the fleet toolchain (rustup stable, trunk, dpkg-deb, chromium).

Authority

docs/RELEASE-ENGINEERING-PLAN.md §5.1; docs/RELEASE-ENGINEERING-PLAN.md acceptance criterion "every required artifact is built from the exact release tag SHA with locked dependencies".

Stopping condition

A dated receipt listing each artifact's path, size and digest, or an explicit statement of which dist command could not run and why.

Verification

cargo run -p xtask -- dist --native && cargo run -p xtask -- dist --web && cargo run -p xtask -- dist --source && cargo run -p xtask -- dist --sbom

Evidence and blockers

Two of the four dist commands are proven on the current tree: the native dist is BUILD VERIFIED (campaign P0.4.3 — native dist built, manifest verified, DEB read back) and the web dist is BUILD VERIFIED (campaign P0.4.4 — web dist built, bridge smoke green).

The other two cannot run on main at all: xtask dist --source and xtask dist --sbom do not exist on main (the dist verb dispatch handles only --web and --native; audit finding F-9). Both were verified on the PR #12 ancestor instead — the source archive at 3.35 MB, sha256 a0fcaafe…, and the SBOM with 493 components, sha256 837a731b… — which is a branch, not the release candidate.

Blocker: the dist --source and dist --sbom verbs landing on main (they ship with the board branch / PR #12); the archive and SBOM work itself is tracked by T27-52 and by issue #32.

Ledger: docs/tasks/T27-06-dist-build-baselines.md and docs/release/EXECUTION-BOARD.md row T27-06 (these land with PR #12).
Campaign: docs/planning/release-compaign/Cross-Platform Releas.txt.

Lingua principale
Rust
Stelle
11
Fork
1
Merge medio
9h 48m
PR unite (30g)
13

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 aliasfoxkde/FireCraft

Tutte le issue di aliasfoxkde/FireCraft

Issue simili

Altre issue su Rust

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.