# Release status

What a ParticleDB release candidate is fit for today, what may change before the GA release, and what GA requires.

Source: https://particledb.ai/getting-started/release-status/

ParticleDB **1.1.19-rc.17** is a **release candidate**. It is not yet generally available.

Use it to evaluate, prototype and test against your own workloads. Don’t use it as the only copy of data you can’t afford to lose.

## What a release candidate means here

| Question | Today |
|---|---|
| Fit for production data | Not yet. Wait for the GA release, or keep an independent copy of the data. |
| Storage format | May change before the GA release. A release may refuse a data directory from an older release candidate. If it does, export and reload the data (see [Upgrades](/guides/upgrades/)). |
| Upgrades | Supported between consecutive release candidates where the [release notes](/installation/releases/) say so. Upgrades are one way. |
| Commands, options and SQL | May change between release candidates. Changes are listed in the release notes. |
| Support | Community support only. No service-level commitment at this point. |
| Security fixes | Issues are fixed in release candidates. Older release candidates may not be patched. |

## Stability by area

| Area | Status |
|---|---|
| SQL tables, indexes and transactions, single server | Release candidate |
| Key-value over the native protocol and the Redis protocol | Release candidate |
| PostgreSQL-compatible clients and drivers | Release candidate. See [ORM compatibility](/connectivity/orm-compatibility/). |
| Studio | Release candidate |
| Vector search | Preview |
| Particles | Preview |
| Replication and clusters | Preview. Not covered by the single-server testing below. |

**Preview** means the feature works and is documented, but its interface and behaviour may change more than the rest of the release candidate.

## How releases are tested

Each release candidate passes the full regression suite. It also passes isolation and anomaly checks: Hermitage isolation tests, Elle history checking, our own invariant tests for lost updates and atomicity, and SQLancer query-correctness testing.

These are our own test runs. They are not an independent audit. The [Jepsen analysis](/installation/releases/) examined earlier pre-release builds.

## What the GA release requires

- A stable storage format, with upgrades supported from the GA release onward.
- No open data-loss or isolation defects.
- Independent re-testing of the transaction and durability guarantees.
- Published benchmark results that can be reproduced, with methodology and scripts.

## Report a problem

Open an issue on [GitHub](https://github.com/particledb-ai) or ask in Slack. Include the output of `particledb --version`.
