Release Plan

Owned by Onesait Platform
Last updated: 02/10/23
2 min read

Every Quarter (Q, three months) we generate a new release by increasing the second digit and establishing a version name.

The content of each release is made according to a product roadmap:

  • The version name is chosen between 80s games of 8 bits and in alphabetical order (Arkanoid, Barbarian, Commando ...)

  • Within a Q we generate 4 stable versions, one at the beginning of the Q and another three during the Q, at the end of the current month. 

  • The stable versions are deployed in the STABLE environment, as https://barbarian.onesaitplatform.com/controlpanel

  • Each week we generate a release candidate version, this version starts from a stable branch of code and increases the third digit of the version (1.3.1-rc1, 1.3.2.rc1, 1.3.2-rc2, ...). It is intended for the resolution of bugs and other improvements detected in the stable version of Q.
    During Q the new functionalities defined in the roadmap are integrated in the develop branch and deployed in the DEV environment: https://development.onesaitplatform.com/controlpanel/

  • Both the release candidate (weekly) and the quarter (quarterly) versions have features (features), fixes (bugs) and improvements (upturns) grouped in Milestones.

  • During the Q, all versions of develop generate an alpha version (1.4.0-alpha1, 1.4.0-alpha2, ...) except for the last week of the Q in which we focus on stabilizing all the developments of this branch and beta versions (1.4.0-beta1, 1.4.0-beta2) are generated until reaching the final stable version, as 1.4.0-commando