Validation and Release Rules

Validation checklist, release rules and the required final report format.

v1StandaardTerug naar overzicht

Inhoud bewerken

Pas de instructie aan. Opslaan maakt een nieuwe versie en is terug te draaien.

Gelijk aan standaard

Voorbeeld

De huidige opgeslagen inhoud.

Toon inhoud (1.078 tekens)

# Validation and Release Rules

When work is actually done.

## Validation checklist
- Page loads.
- Main workflow works.
- Main action works.
- Navigation still works.
- TypeScript check run if available.
- Lint run if available.
- Build run if appropriate.
- Empty, loading and error states considered.
- UI is clearer than before.
- Settings are still centralized.
- No obvious duplicate components added.
- Documentation updated if needed.
- Changelog updated if meaningful.

## Release rules
- Do not mark work as done without stating what was checked.
- Do not push unfinished work as complete.
- Do not ignore build, type or lint errors.
- If tests cannot be run, explain why.
- If a change affects users, document the impact.
- If rollback is relevant, document rollback notes.
- When work is checked and ready for review, the default next step is to publish to staging for stakeholder testing unless told otherwise.

## Required final report format

Done:
- ...

Why it matters:
- ...

Files changed:
- ...

Validation:
- ...

Known issues:
- ...

Remaining work:
- ...

# Validation and Release Rules When work is actually done. ## Validation checklist - Page loads. - Main workflow works. - Main action works. - Navigation still works. - TypeScript check run if available. - Lint run if available. - Build run if appropriate. - Empty, loading and error states considered. - UI is clearer than before. - Settings are still centralized. - No obvious duplicate components added. - Documentation updated if needed. - Changelog updated if meaningful. ## Release rules - Do not mark work as done without stating what was checked. - Do not push unfinished work as complete. - Do not ignore build, type or lint errors. - If tests cannot be run, explain why. - If a change affects users, document the impact. - If rollback is relevant, document rollback notes. - When work is checked and ready for review, the default next step is to publish to staging for stakeholder testing unless told otherwise. ## Required final report format Done: - ... Why it matters: - ... Files changed: - ... Validation: - ... Known issues: - ... Remaining work: - ...