Skip to content

Enhance schema for the version number in the application description #143

@ajcraig

Description

@ajcraig

Feature description

Goal: Provide additional clarity on how Application developers should version manage their applications.

** Category **

  • Application Description File

Provide adequate technical acceptance criteria(s) associated with this feature below:

  • Improved schema for application version numbers
    • Current specification states this is a string which is inadequate to properly manage workloads.

Although not required, it is highly encouraged to provide feature use-cases below:

  • Application version management via app suppliers and wfm suppliers

Additional information

  • Create a PR to update the specification to indicate that the version schema should match the semantic versioning specification
  • Margo does not infer any meaning behind the versioning but just validates it matches the semantic versioning specification so versions can be compared
  • Storm (SIEMENS): Note: We should get this "right" from the (GA) start as imposing that later is a recipe for breakage.Semantic Versioning is pretty standard and should be used anyway.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    Status

    Todo

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions