Announcing a New Versioning Strategy

There’s a lot of changes happening at Event Store, with an increase in team size and a new vision for taking Event Store to the next level.

As part of these changes, we are updating our versioning and release strategy. This is to make it clearer to our customers when they can expect a new release and how long we will support it for.

From the next release (that would have been called V6) we will commit to putting out three supported releases a year in February, June and October.

These releases will be versioned with the year and month, for example:

  • 20.2
  • 20.6
  • 20.10

The February and June releases will be normal releases and we will support them for a period of 4 months. The October release will be our long term support (LTS) release and we will support them for a period of 24 months, until October 2022.

There will still be patch releases between major versions to address bugs and possible performance improvements.

Alongside these new versions, we are introducing nightly and stable builds. We will release the nightly builds each day and the stable builds on a semi-regular basis. We won’t support these builds but they will offer our customers the opportunity to get early access to new features. It will also give some visibility as to what is expected in the next official release.

The nightly builds are already available and stable builds will become available soon after the 20.6 release.

Finally, we will be breaking cadence between the client and server releases. This is mainly due to us introducing clients in multiple languages such as .NET, Java, Go, and NodeJS. These clients will generally be versioned separately and newer clients will follow a more traditional strategy starting at v1.0.0. The latest released versions of each client will support both current and previous releases of EventStoreDB where possible. Each client will state in its own release notes which versions they support, and pre-release versions of clients may not support the full range of server versions.

Photo of Mat McLoughlin

Written by: Mat McLoughlin

Mat is Event Store's Head of Product and Developer Advocacy; he uses his previous experience as an Event Store customer building event-sourced systems to identify areas where the developer experience can be improved, and his objective is to help more developers learn and successfully implement Event Store in their systems.

Related posts

New EventStoreDB Java Client

Mat McLoughlin,

Event Store is pleased to announce the open-sourcing of a new supported GRPC-based Java client for EventStoreDB. Releasing the new EventStoreDB Java client is representative of Event Store’s intent to have fully supported, first-class clients for every major platform.

Event Store Announces EventStoreDB Name Change

Mat McLoughlin,

We are pleased to announce a name change to our core product: the current Event Store open source database technology will be renamed EventStoreDB. "There are two major reasons for the name change. One is to make it as clear as possible that the flagship Event Store technology is a database technology. We had occasional feedback that this wasn't completely clear. Two, it makes room for other products that are on Event Store's roadmap and...

Event Store Has a New and Improved Community Forum


We are pleased to announce our new forum is now live at! It replaces our Google Group as the primary place for our community of developers to connect with other users and the team behind Event Store, to ask questions, find answers, and discuss all things Event Store with the rest of the community. It also acts as a great way for the community to provide us with vital feedback to help us understand...