Versioning of distribution and apps
Some time ago, @hansegucker and I discussed the version numbering.
Currently, we release all apps, and the default distribution, with synchronised, semantic versions (we would next release all official apps, and the core, al lset to the version
However, we considered a situation where we do regular reelases of the default distribution, but without changes in some apps. In that case, bumping the version would contradict the semantic versioning principle. We thus considered it better to version all apps separately strictly adhering to semantic versioning, and release the default distribution under its own version number. Forthat, we thought we could divert from semantic versioning, and just use the
year.month versioning scheme, or something like that.
Then, do we even need to release the distribution under a specific version? Couldn't we just relesae apps, and have the default distribution be a rolling release of the most recent versions of all official apps? Technically, the distribution version has no meaning whatsoever. Its primary and only reason is marketing, because we can sell it as something big and new with a fancy code name.
What would all that mean for our milestone planning? Would we track milestones separately per app agian, or set common targets for the default distribution like we do now?