Skip to content

This page describes how version and revision information on this site is recorded, reviewed and corrected.

How a value is recorded

  1. Confirm the value. A version or revision is added only when it has been confirmed on hardware and tools the site owner is authorised to use.
  2. Record the facts. The value is stored with its revision, its firmware relationship where known, its documented compatibility, a source note and a review date.
  3. Mark the status. Each record is marked as verified or unverified. An unverified record is published for reference and labelled clearly.

What we will not do

  • Publish a version or revision number we have not confirmed.
  • Copy a value from another site without a stated source.
  • Infer a firmware relationship that has not been observed.
  • Reproduce key material under any circumstances.

Re-checking

A stated value is as accurate as the review date shown on its record. If a review date is old, treat the statement as historical rather than current.

Corrections

Report a correction through the contact page. Confirmed corrections are applied, and where they change the substance of a page, the record is updated rather than replaced — the connected pages read from the same data, so a single correction propagates.

Why the model is structured this way

Version data and the pages that explain it are connected: a version feeds the versions hub, which feeds the compatibility hub. Updating a value in one place rather than rewriting several articles is what keeps those pages from contradicting each other.