Does HL7 allow FSH to be semantically versioned?

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive
    • Priority: Medium
    • Shorthand (FHIR)
    • 0.12.0 [deprecated]
    • FHIR Infrastructure
    • Language Reference
    • 3.1.1 Versioning
    • Hide

      FSH actually does not follow semantic versioning, since FHIR’s balloting practices do not follow semantic versioning. Following FHIR practice, our “pre-release” ballot edition for FSH 2.0 should be 1.x – which means we’d be using a minor version increment even though there are major changes.  The specification should not claim to use semantic versioning. Will be removed/rewritten to explain how versions are actually assigned.

      Show
      FSH actually does not follow semantic versioning, since FHIR’s balloting practices do not follow semantic versioning. Following FHIR practice, our “pre-release” ballot edition for FSH 2.0 should be 1.x – which means we’d be using a minor version increment even though there are major changes.  The specification should not claim to use semantic versioning. Will be removed/rewritten to explain how versions are actually assigned.
    • Kramer/Rhodes: 14-0-0
    • Correction
    • Compatible, substantive

      I would love for FSH to follow semantic versioning, but my understanding is that HL7 / FHIR don't allow true semantic versioning. E.g., ballot versions are minor increments of published major versions, even though the ballot version may contain major changes. We need to chase this down.

      Existing Wording:

      The FSH specification, like other IGs, follows the semantic versioning convention (Major.Minor.Patch).

            Assignee:
            Unassigned
            Reporter:
            cmoesel
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: