Open Horizon should more completely support semantic versioning (semver). Currently oniy: "N", "N.N", and "N.N.N" semvers are supported.

Overview

I think we should fully support the current semver syntax, semver 2.0 (https://semver.org).

Design

Likely this would require multiple changes.

User Experience

Users often use the widely known semver syntax (e.g., "1.0.1.23" or "2.1.5-beta") only to have this rejected by Open Horizon.

Command Line Interface

(none)

External Components

(none)

Affected Components

(unknown – likely many)

Security

<Describe any related security aspects of the solution. Think about security of components interacting with each other, users interacting with the system, components interacting with external systems, permissions of users or components>

APIs

<Describe and new/changed/deprecated APIs, including before and after snippets for clarity. Include which components or users will use the APIs.>

Build, Install, Packaging

<Describe any changes to the way any component of the system is built (e.g. agent packages, containers, etc), installed (operators, manual install, batch install, SDO), configured, and deployed (consider the hub and edge nodes).>

Documentation Notes

<Describe the aspects of documentation that will be new/changed/updated. Be sure to indicate if this is new or changed doc, the impacted artifacts (e.g. technical doc, website, etc) and links to the related doc issue(s) in github.>

Test

<Summarize new automated tests that need to be added in support of this feature, and describe any special test requirements that you can foresee.>