-
Notifications
You must be signed in to change notification settings - Fork 10
Release Procedure
For a sample version as 0.41.3, each of the numbers denote:
- 0 -> Public release version
- 41 -> Major release version
- 3 -> Minor release version
The main branch will be regularly updated by programmers from their code
branches, and promoted will be continuously merged into main.
After QA and validation, main branch will be merged into staging for a release,
and the changelog will be reflected into promoted branch once deployed.
Internal playable builds will follow these updates.
The promoted branch will be reflected into stable branch after QA process by programming & creative team leads. This will be released as a playtester playable build.
The release branch will be updated with code and engine updates from stable, after an approval for enhanced stability and quality by the programming & creative team leads. Public playable builds will follow these version updates.