Uploaded image for project: 'Thorntail'
  1. Thorntail
  2. THORN-838

Config API's version number should be >= 1

    Details

    • Type: Enhancement
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 2017.2.0
    • Component/s: config-api
    • Labels:
      None
    • Sprint:
      2017-Jan-A

      Description

      Swarm heavily depends on the Config API and any breaking changes in the Config API would break Swarm's public API. Hence, the Config API's interface is essentially stable. The project should reflect that by using a version number >= 1.

      (I believe it's a common knowledge, spread particularly by SemVer, that major version number 0 means "unstable".)

      I'm specifically not suggesting that the Config API should adopt any particular versioning style, using any kind of .Final version qualifiers etc.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                bob.mcwhirter Bob McWhirter
                Reporter:
                lthon Ladislav Thon
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: