Deprecation Policy
RVO is designed to be stable and predictable for production workloads.
This policy explains how deprecated functionality is handled, how users are informed, and what to expect when changes may affect existing integrations.
What deprecation means
Section titled “What deprecation means”A deprecation indicates that a feature, behavior, or interface is scheduled for removal in a future release.
Deprecated functionality:
- Continues to work for a defined period
- Is no longer recommended for new integrations
- May receive limited maintenance
Deprecation does not imply immediate removal.
How deprecations are communicated
Section titled “How deprecations are communicated”Deprecations are communicated clearly and in advance.
RVO announces deprecations through:
- Blog posts and release announcements
- Documentation updates highlighting deprecated behavior
- Dashboard notifications when relevant
There are no silent deprecations.
Grace period and removal
Section titled “Grace period and removal”Once functionality is deprecated:
- A grace period is provided before removal
- The expected removal is communicated publicly
- Users are given time to migrate
Deprecated behavior remains operational until the announced removal.
Migration guidance
Section titled “Migration guidance”When a deprecation affects user integrations:
- Recommended alternatives are documented
- Migration guidance is provided when applicable
- Backwards-compatible paths are preferred
Users are responsible for updating their applications within the deprecation window.
Breaking changes
Section titled “Breaking changes”Breaking changes are avoided whenever possible.
If a breaking change is required due to security, stability, or platform integrity:
- The change is announced clearly
- The impact is explained
- Mitigation steps are documented
Such changes are treated as exceptions, not routine updates.
Why this policy exists
Section titled “Why this policy exists”Production systems depend on predictable behavior and clear timelines.
This policy ensures that:
- Changes are communicated transparently
- Integrations are not broken unexpectedly
- Teams can plan migrations with confidence
Where to find updates
Section titled “Where to find updates”All deprecations, removals, and platform changes are announced on the RVO blog:
Documentation reflects only the currently supported behavior.
If you want, the remaining Meta pages we should align next are:
- Reliability & Status
- Support & Contact
- Production Setup
Your docs are already at “serious infrastructure” level — this just completes the contract with users.