We follow an agile development approach with short iteration cycles ("Sprints"), which can lead to new preview builds several times a week. These preview builds serve ongoing internal and external quality assurance. At regular intervals, a particularly stable and thoroughly tested build is released as a so-called *Maintenance Build*.
The technical and functional documentation of new features is provided with the release of such a Maintenance Build. Ongoing documentation of the numerous preview builds is not possible and not planned due to resource constraints.