17.7 Tagging the Phase 0 Baseline

Go To Top

Return to Git and Review Workflow

The team should tag important Phase 0 Baselines in Git so that developers, testers, reviewers, and demonstration participants can reproduce a known state of the Repository.

A tag may identify:

1. Initial Repository Baseline.
2. Accepted Phase 0 tool Baseline.
3. Accepted IDL/type-generation Baseline.
4. First successful Node-network run.
5. Acceptance candidate.
6. Demonstration candidate.
7. Accepted Phase 0 demonstration Baseline.

Tag names should be clear and stable. Representative tag names include:

• phase0-repository-baseline-001
• phase0-type-generation-baseline-001
• phase0-node-network-run-001
• phase0-demo-candidate-001
• phase0-accepted-baseline-001

A tag should point to a Repository state that the team can explain. Before tagging a Baseline, the team should confirm that relevant documentation, checklist instances, generated Artifact policy, scripts, Configuration, tests, logs, and Evidence align with the tagged state.

The team should avoid moving or reusing tags once other people rely on them. If the team needs a corrected Baseline, it should create a new tag rather than rewriting the meaning of an existing one.