Release Cycles

For each release in the iOSiOS The operating system used on iPhones and iPads. and Android app projects, we follow roughly the same basic plan to ensure stable releases that are sufficiently tested.


A few days (at most) to finalize what should be worked on, who’s working on what, and setting a target date.


Development begins, nightly betas are issued.

A push for localization is made towards the end.

QA Testing (Code Freeze)

Testing begins, the whole group has to test and sign off on each release. If the lead dev finds a critical bug that has to be fixed the testing is reset.

RCRelease Candidate A beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge.

By now, the release should be stable, having passed QA. The RC is released and a push is made for the community to use it as their everyday WordPress app.

Write announcement posts, update screenshots and app store descriptions.

Start scoping next release.


The update is submitted and announced.

Last updated: