Release cycles

Conventional thinking says that "every end of sprint means a deployment". We no longer do that but rather implement a "continuous deployment" process where we deploy improvements on a daily basis which we call "stability/maintenance releases".

We believe that high performing teams should always provide value to the business even in small increments.

How we do releases:

1. Maintenance releases (minor versions)
2. Feature releases (major versions)

Release characteristics:

1. Testability
2. Revertability
3. Small batches

For early stage projects:

1. Even under heavy development, every deployment in a production environment is targeted under "v0.1.x" series.
2. For MVP (beta), we start our version as "v1.x.x"

More about this topic in our "versioning".

Check out how we do our releases