Establish a Clear Release Cadence and Roadmap

First of all, thank you for all the work that goes into this project.

One thing that has become increasingly difficult as a downstream user is understanding when stable releases are expected. At the moment, it seems that RC (release candidate) versions are published very frequently—sometimes daily—but there isn't a clear release cadence or roadmap for when those RCs are expected to become stable releases.

## Why this matters

For teams that depend on the project in production, it's hard to answer questions such as:

* Should we adopt the latest RC?
* Is another RC expected tomorrow?
* Is a stable release likely this week or next month?
* Is the current RC considered feature-complete or still under heavy development?

Without a predictable release process, planning upgrades becomes much more difficult.

## Suggestion

It would be extremely helpful to define and communicate a release cycle, for example:

* A target cadence for stable releases (e.g. every 2, 4, or 6 weeks).
* Clear criteria for when an RC is cut and what is expected before it becomes stable.
* A rough roadmap or milestone indicating what the next stable release aims to include.
* Expectations around how long an RC phase typically lasts.

The exact cadence is less important than having something predictable that users can plan around.

Thanks again for maintaining the project.

The issue does not name any files, tests, or release entry points to inspect. First review the project's current release process and existing milestones or documentation, then determine whether maintainers agree on a cadence, RC criteria, roadmap, and expected RC duration; done means those expectations are agreed and communicated.

Written by the indexing model from the issue text.