use semver for device packages?

Our packaging policy says:

A special case are packages without upstream sources (e.g. main/postmarketos-base), where the source files are included in the package directory. In those cases, the packaged sources should be treated as upstream sources, and the pkgver should increase when they are edited.

However this leads to the pkgver racing up fast in device packages, and it's not possible to judge whether a change contains new features or is just a fix. Or even a major change like downstream kernel -> mainline kernel. So I'm wondering whether we would want to use semver instead.

If we decide to do so:

• just add the digits to the existing pkgvers for compatibility, e.g. pkgver=11 -> pkgver=11.0.0
• adjust pmbootstrap aportgen code to start device packages with 0.1.0
• add CI test to make sure we use semver for device packages moving forward

Thoughts?