Baselines and publishing

A baseline is a frozen, signed snapshot of approved records: the design history at a point in time.

1. 1Release readytrace complete, nothing blocking
2. 2Create baselinedocument control
3. 3Publishall or nothing, to the chosen repository
4. 4Export packagefor audits and submissions

#Create and publish

When the project is release ready, document control creates a baseline from Project → Baselines and publishes it to the chosen repository: Jira, Polarion, SharePoint or the archive. Publication is all or nothing.

Each baseline brings the repository in line with Tracewright: links are updated, items deleted in the repository are re-created, and items of obsolete records are marked withdrawn.

#If a publication fails part-way

If a failed publication can't be fully rolled back, the baseline shows failed partial with the leftover items. Document control cleans them up in the repository and confirms it (Confirm clean-up) before anything else can be released.

#Export

The full export package (records, trace, signatures, audit trail and a README stating the project's scope and standards) is available from the baseline, for audits and regulatory submissions.

#Obsolete records

Document control makes an approved record obsolete when it's no longer wanted; any open draft of it closes too. The next baseline marks its item withdrawn in Jira or Polarion.