Our release cycle is based on a sprint of 2 weeks, with every sprint resulting a potentially releasable version of the application. A new release contains newly developed and/or fixed features. Releases are named according to semantic versioning: `[major].[minor].[patch]`, for example: v1.16.7

The APEXX product owner is responsible for determining if at the end of a sprint the work is fit for a new release. If the work is not accepted, it may be cancelled or postponed. The items worked on in a sprint are therefore not a guarantee, unless agreed otherwise.