LogoLogo
Back to Speedb.io⭐ GitHubDiscord
  • 👋About
    • Speedb Use Cases
    • Speedb Communication Channels
    • Release Cadence
    • Releases
    • Roadmap
  • 💻Getting started
    • Speedb Quick Start Example
    • Dependencies
    • How to Compile Speedb
    • Drop-in Replacement
    • Use prebuilt binaries
    • How to contribute
      • Contribute code
      • Feature request process
      • Submit a pull request
      • Add or update documentation
      • Report bugs and other issues
      • Help with new and ongoing feature development
    • Kafka Streams: How to use Speedb instead of RocksDB?
  • ✨Speedb Features
    • Memory Tracking
    • Speedb Tuning Function
    • Table Pinning Policy
    • Snapshot Optimization
    • On Thread Start Callback
    • Write Flow
    • Global Delayed write
    • Live Configuration Changes
    • Report Index Size per Column Family
    • Proactive Flushing
    • Sorted Hash Memtable
    • Paired Bloom Filter
  • ➕Enhancements
    • Range Delete Improvement
    • Dynamic Delayed Writes
    • Reduce switch memtable latency
  • 🛠️Tools
    • Log Parser
    • DB_bench: Groups
    • Beezcli Tool
  • 🔦RocksDB Basics
  • 📈Performance testing
Powered by GitBook
On this page

Was this helpful?

Edit on GitHub
  1. About

Release Cadence

Speedb releases follow the usual major.minor.patch semantic versioning schema.

Major versions

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

Upgrading to a new major version may require some code changes.

Minor versions

Minor versions usually contain extended functionality, without breaking compatibility.

Upgrade to a new minor version is expected to be seamless

Patches

Patch-level versions consist primarily of backward-compatible bug fixes.

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

Upgrading from the previous patch version is expected to be seamless.

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

PreviousSpeedb Communication ChannelsNextReleases

Last updated 2 years ago

Was this helpful?

👋