Versioning
Each part of yadoms follows a version engine.
Yadoms is versioned as follow : XX.YY.ZZ where:
- XX is the major version of Yadoms
- YY is the minor version of Yadoms
- ZZ is the revision number of Yadoms
Each extension is versioned as follow : XX.YY.ZZ where:
- XX is the major version of the component
- YY is the minor version of the component
- ZZ is the revision number of the component
All components can have 3 release types :
- Beta: this release type is used near the end of the development. Users can begin testing it but software is un-stable. New functionalities can be added or removed at any time.
- Release Candidate: Development phase is finished. Users can install it and use as is. Tickets that indicates bugs are welcome.
- Stable: This version has been fully tested, main bugs are fixed and Yadoms team has validated it.
When your are participating to Yadoms development (Thanks !!), You must choose your release type.
At the beginning of your component, your first delivery is under Beta version.
When you make some fix to your Beta, you can stay in Beta version increasing the minor version number or go to Release candidate at the same minor version number if there is no relevant opened tickets.
When there is no more tickets noticed by the community after a little period, you can go to Stable version.
As an example, you can follow all steps in annotated life cycle above.
Yadoms -- The ultimate house automation solution