Release Cycle

Reviactyl follows a predictable release cycle designed to balance stability, long-term support, and rapid improvements.

Versioning Scheme

Reviactyl uses CalVer for versioning, which is based on the release date. The format is YY.MM.MINOR, where:

• YY is the year of the release.
• MM is the month of the release.
• MINOR is the minor version number.

v26.05.1 indicates a release in May 2026, with a minor version of 1.

Development Timeline

Development for a new yearly release cycle typically begins in February.

During this period:

• New features are developed
• Internal changes are tested
• APIs may change
• Experimental/Insider builds may be published

Initial Public Release

The YY.MM.0 release is the first public rollout release.

It is intended to gather wider real-world feedback after internal and beta testing.

Example: v26.05.0 would be the initial public release for the May 2026 cycle.

This release may still contain:

• Edge-case bugs
• Upgrade issues
• Performance regressions
• Compatibility issues

Users who prefer maximum stability are encouraged to wait for the YY.MM.01 release.

Stable Release

The YY.MM.01 release is the first stable release of the cycle.

This release focuses on:

• Fixing critical bugs
• Improving performance
• Ensuring compatibility
• Addressing upgrade issues

Support Policy

Each release cycle is supported for a minimum of 12 months after the initial public release. During this time, critical bug fixes and security patches will be provided.

After 12 months, the release will enter a maintenance mode where only critical security fixes will be provided, and users are encouraged to upgrade to the latest release cycle for continued support and new features.

For more information on support policies, please contact contact@reviactyl.dev