Patching Standards
Active Evaluation FINOS Labs This material is provisional and has not been published as a formal FINOS standard.
Home / Standards / FORK-003
FORK-003

Baseline Tags

Every backpatch line identifies its starting source SHA with a `v+backpatch.baseline` tag.

Status
Draft
Category
Fork Management
Applies to
Patch providers, Enterprise recipients

Requirement

Patch providers MUST tag the commit that represents the baseline source state for a backpatched version.

The tag MUST use the form:

v<VERSION>+backpatch.baseline

This tag scheme applies regardless of the upstream project tag convention.

Rationale

Recipients need an unambiguous starting point for source comparison, provenance review, and audit evidence.

Evidence

Patch evidence SHOULD include the baseline tag, the commit SHA it resolves to, and the corresponding upstream version or artifact.

Observed OSERA examples

Public OSERA repositories currently include baseline tags such as:

  • backpatch-spring-framework: v5.3.39+backpatch.baseline
  • backpatch-gson: v2.8.8+backpatch.baseline
  • backpatch-activemq: v5.14.5+backpatch.baseline
  • backpatch-logback: v1.2.9+backpatch.baseline