Process

Backward-compatibility rules

How versions evolve without breaking existing implementations.

  1. Additive only within a major version. A minor version (0.1 → 0.2, 1.0 → 1.1) may add optional fields, objects and enum values. It never removes a field, makes an optional field required, or changes a field's type or meaning.
  2. Ignore what you do not know. Receivers must ignore unknown fields and unknown ext members instead of rejecting the message. Senders must not depend on a receiver understanding a new field.
  3. Never repurpose. A field name or enum value, once published, keeps its meaning forever. A changed meaning gets a new name.
  4. Enums are open. Receivers treat an unknown enum value as "unknown / other", never as an error, unless the spec marks the list as closed.
  5. Extensions live in ext. Our specs extend OpenRTB only inside ext objects and never redefine core OpenRTB fields.
  6. Defaults are explicit. If a field is absent, the documented default applies; a new field's default must reproduce the old behaviour.
  7. Breaking changes need a major version (1.x → 2.0), a migration note, and a parallel-support period.
  8. Deprecation window. A deprecated field stays valid for at least 12 months (or two minor versions, whichever is longer) after the deprecation is published.
  9. Schemas follow the same rules. JSON Schemas set additionalProperties to allow extension and carry the version in $id.
  10. Every change is in the changelog with the section affected and whether it is additive, a fix, or breaking.