> For the complete documentation index, see [llms.txt](https://docs.reviactyl.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.reviactyl.app/project/release-cycle.md). # Release Cycle Reviactyl follows a predictable release cycle designed to balance stability, long-term support, and rapid improvements. ## Versioning Scheme Reviactyl uses [CalVer](https://calver.org/) 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.app` --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.reviactyl.app/project/release-cycle.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.