Release candidate: complete final v1 acceptance and release checklist

Aperta
#27 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
8/100
Tipo di issue
Funzionalità
Chiarezza
Da chiarire
Stato di attività
Attiva
Stack tecnologico
typescript
Ambito
release, testing

Direzione di ricerca

Start by reading the prerequisite work: Issue #20 for browser-verification requirements, and the release-readiness issues for package consumption, license/versioning policy, and clean-checkout reproducibility. The payload names no specific files or tests. Done means every acceptance checkbox has recorded commands, results, browser details, the commit SHA, and the proposed version and tag, pending maintainer approval. Publishing is out of scope.

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

Descrizione

Goal

Produce a verified DevLens v1 release candidate after the outstanding visual, packaging, policy, reproducibility, browser, and documentation work is complete.

Dependencies

Complete these issues before closing this issue:

  • #20 Panel visual styling and theme contract
  • #24 Package publishing and external consumption
  • #25 License and release/versioning policy
  • #26 Clean-checkout reproducibility and required CI checks
  • #28 Fresh clean-checkout validation baseline
  • #29 Real-browser smoke verification
  • #30 Release-facing documentation and evidence reconciliation

Final acceptance checklist

  • All prerequisite release issues are complete or explicitly waived with rationale.
  • Full tests, typecheck, build, formatting, and diff checks pass.
  • Real-browser verification is recorded with the tested browser/environment and results.
  • Packed artifacts pass the external consumer fixture.
  • Public documentation and metadata match the actual release contents and policy.
  • README test-count and other quantitative claims match fresh evidence.
  • License and version metadata are internally consistent.
  • Required CI/reproducibility checks are established and green.
  • No unresolved release-blocking defects remain.
  • The proposed release commit, version, tag, and release notes are identified for final approval.

Release execution

After acceptance:

  • Confirm the final release commit SHA.
  • Confirm the final version.
  • Prepare the release tag.
  • Prepare release notes.
  • Obtain explicit approval before publishing packages or creating the public GitHub release.

Out of scope

  • New v1 features.
  • Publishing packages or creating a public GitHub release without explicit approval.
  • Reopening documented v1 non-goals without a concrete release blocker.

Verification

Record exact commands, results, browser checks, commit SHA, proposed version/tag, and known limitations. A green unit-test count alone is not sufficient evidence for release readiness.

Lingua principale
TypeScript
Stelle
1
Fork
0
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

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 Mystify7777/devlens

Tutte le issue di Mystify7777/devlens

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.