The kdb Version consinsts of Major, Minor and Micro fields, defined in kdb.h:
#define KDB_VERSION "0.7.0rc2" #define KDB_VERSION_MAJOR 0 #define KDB_VERSION_MINOR 7 #define KDB_VERSION_MICRO 0rc2
KDB_VERSION is a string holding the whole information suitable to be printed out.
In Short MAJOR=0 (Situation now)
But For MAJOR>0 (after Elektra 1.0.0 Release)
MAJOR will be sticked to zero until we are forced to raise it up to 1.0.0 to show that so many programs use elektra and backends implement the backend-API that we can't change anything in the API.
MINOR means before 1.0.0 that some API changes are done. Consult the NEWS, Homepage and Documentation for changes. You may need to recompile all your applications depending on elektra for a MINOR transition. But it gets more and more unlikely that it will happen toward 1.0.0. 0.7 is in a really good API shape in most parts.
MICRO is the indicator for Bug fixes. Since 0.7 neighter API nor ABI changes will be done and the version will be maintained for at least one year after release.
