Understand documentation versions and releases

Choose the version that matches the product

Label	Meaning	When to use it
Next	A preview being prepared for a future product release. It can still change.	Use it to review upcoming documentation, not as proof of current product support.
Current release	The newest approved documentation snapshot for an identified product source.	Use it when its product version matches your installation.
Older release	An unchanged snapshot for an earlier product version.	Use it when your installed product still matches that version.

Check the release identity

A released version page shows the exact product version, release date, and trusted product tag or commit. The documentation snapshot also has a content hash.

A local development snapshot is not an official supported release unless the approved product release record says it is.

Read all release information

• Release notes explain approved additions, changes, fixes, and breaking changes.
• Known problems explain verified symptoms, impact, and safe workarounds.
• Supported versions come from the approved support policy.
• Deprecation notices explain an approved future removal and replacement.
• Upgrade guidance gives a tested path between exact versions.

If one of these pages is absent, do not guess its answer.

Do not use unverified upgrade steps

Upgrade steps are published only after the product process is stable. The exact source and target path must pass backup, restore, upgrade, result, and rollback checks.

Until then, keep using the approved process for the installed product version.

Older releases do not change

A released page is an immutable snapshot. Its screenshots, examples, API contract, and offline download remain tied to that release.

A later correction belongs in a new, clearly identified documentation release. The original snapshot remains available for evidence.

Open help from your installation

Help for this page uses the version stamped into the installed Product. A released build opens its exact documentation version. Local development builds can open Next.

The guide warns when the Product revision supplied by Help differs from its reviewed revision. Check that warning before following instructions.

If matching documentation is unavailable, use the matching offline download or contact your installation owner. Do not substitute newer instructions.

Check build details

Each guide shows its Product revision. A frozen version also records the Product build, documentation revision, and hashes for its content and downloads.

Use the build details and matching API contract linked from that version. Feedback is recorded with the selected documentation version and page.

Use the version picker

Choose the version near the page title. Search results stay inside that version. Check the version again before following an administration, API, or upgrade instruction.

For release authors

Complete the release notes, known problems, support, deprecation, upgrade, and review templates. Remove every instruction and missing value before approval.