# Release Cadence

Speedb releases follow the usual major.minor.patch semantic versioning schema.&#x20;

**Major versions**

Major versions introduce new capabilities and significant changes. It's possible that these versions don't maintain backward compatibility.&#x20;

{% hint style="info" %}
Upgrading to a new major version may require some code changes.&#x20;
{% endhint %}

#### Minor versions

Minor versions usually contain extended functionality, without breaking compatibility.&#x20;

{% hint style="info" %}
Upgrade to a new minor version is expected to be seamless&#x20;
{% endhint %}

#### Patches

Patch-level versions consist primarily of backward-compatible bug fixes.&#x20;

Default values may also be changed with patch versions, as long as they don't impact the system.&#x20;

{% hint style="info" %}
Upgrading from the previous patch version is expected to be seamless.
{% endhint %}

### Release schedule

Our goal is to release a new version approximately every two months.

* The version number will be based on the content and semantic versioning
* Any critical bug fixes will be resolved outside of the release cycle.
* We will rebase to a newer Rocksdb version occasionally, changing the release number accordingly


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.speedb.io/readme/release-cadence.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
