Release Channels: stable and preview
StableThe Stable vs Preview/Demo policy and how pages are labeled.
Updated: March 5, 2026
SPG99 documentation uses release-channel labels. They help users immediately understand how much they can rely on a specific capability in production.
Stable
Stable is the main supported contract.
For the user, this means:
- the functionality is intended for normal operation;
- changes are accompanied by documentation and a changelog;
- breaking changes do not happen silently, without a visible transition period.
Preview
Preview is a feature or scenario that can already be tested, but its behavior may still change faster than usual.
In practice, this means:
- use preview only where you are ready for changes;
- for production-critical scenarios, rely primarily on stable sections;
- if a feature is important for your launch, align expectations with the platform team in advance.
How this works in practice
Changes do not go directly into the production environment: before reaching the main delivery, they are tested in test and pre-production stages. The user does not need to know how those stages are built — what matters is that the production environment receives already tested changes, and preview labels help separate the stable contract from early access.
How to read the documentation
- if a page is marked
stable, treat it as the main working instruction; - if a page is marked
preview, treat it as a useful but more fluid scenario; - if you are unsure which mode you need, always choose stable for production.
