Feature #797
Reconstruct versioning handling
Status:
Neu
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
06/01/2026
Due date:
% Done:
0%
Estimated time:
CS Zielversion:
Description
Major-minor versions do not make much sense fort hardware info.
An Main/Generic- and an custom/individual-version would be better.
Main-version has to match exactly, Custom-version is optional and can be handled by application.
Add CONFIG_BIWAK_RETAIN_VERSION_STRICT.
A Check that the minor version must not be higher is also missing. Is this even true?
At the moment there is no possibility for an migration path.