Versioning and support policy
How releases are numbered, how long each one gets patches and which platforms TeselaDB runs on.
Numbering
Each release is numbered MAJOR.MINOR.PATCH. What a new release brings and what you have to do to install it depend
on the number that goes up. With a patch or a minor release it is enough to replace the binary node by node, while with
a major release you read its notes first because it can bring breaking changes.
| What goes up | What it brings | What you have to do |
|---|---|---|
| Patch | Bug fixes only | Replace the binary node by node |
| Minor | New features | Replace the binary node by node |
| Major | Can bring breaking changes | Read its notes, adapt your application and replace the binary node by node |
When a TeselaDB release starts announcing a more recent MongoDB version, its notes say so. Its new features turn on
once every node has it and you raise featureCompatibilityVersion to that MongoDB version with
setFeatureCompatibilityVersion, as in MongoDB.
How long each release is maintained
The latest minor release and the one before it get patches. When a new minor release comes out, the one before those two stops getting them. For example, when 0.3 comes out, 0.3 and 0.2 get patches and 0.1 stops getting them.
Upgrade from one minor release to the next without skipping any, because the node-by-node upgrade is tested between one minor and the next.
Platforms
| Platform | Use |
|---|---|
| Linux x86_64, native and in Docker | Production and development |
| Linux aarch64, native and in Docker | Production and development |
| macOS Apple Silicon | Development, with no latency guarantees |