Release Cycle

📎 Versioning

We follow Semantic versioning for releases.

🧭 Release cycles

For fun-bots we have 3 different release cycles.

Versions follow semantic versioning.

• Stable releases follow the MAJ.MIN.PATCH pattern;
• Release candidates follow the MAJ.MIN.PATCH-RC𝑥 where 𝑥 is the incremental release candidate number;
• Development builds are released as MAJ.MIN.PATCH-DEV𝑥 where 𝑥 is the incremental development release.

🚀 Stable releases

A release becomes stable once the latest release candidate has passed all verifications and tests and no game-breaking bugs or issues were reported or found.

🐛 Release candidates

Release candidates have all features designed, coded and tested, but before releasing a full release we want to allow the community to test it before releasing it fully for production. A release candidate becomes a full release once the fun-bots maintainers agree that no entirely new source code or features will be added to the release. There could still be source code changes to fix defects, changes to documentation and data files, and peripheral code for test cases or utilities.

🔧 Development builds

Ocasionally, we release new features, fix bugs and issues or make any other change to the project. These will become development builds which have not been tested.

Do not run development builds on production, but please help us by testing development builds and reporting issues so we can fix them before they become a release candidate!