[OASIS Issue Tracker] (CAMP-182) CAMP specification versioning

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ https://issues.oasis-open.org/browse/CAMP-182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=59296#comment-59296 ] 

Martin Chapman  commented on CAMP-182:
--------------------------------------

Lets not conflate Anish's issue of specification document version  with the versioning resource that a provider must support. Lets just focus on the former - should the next edition be camp 1.1.1, camp 1.2, or camp 2.0. If the current version resource model is insuffient raise a separate issue.

> CAMP specification versioning
> -----------------------------
>
>                 Key: CAMP-182
>                 URL: https://issues.oasis-open.org/browse/CAMP-182
>             Project: OASIS Cloud Application Management for Platforms (CAMP) TC
>          Issue Type: Bug
>          Components: Spec
>            Reporter: Anish Karmarkar
>            Priority: Minor
>
> We have CAMP 1.1 Committee Spec (CS). We are waiting for two implementations to move it to OASIS Specification (OS). As new issues are filed and we resolve them the spec may change. What is our versioning scheme? Does backward/forward compatibility affect our versioning scheme. As a point of reference, CAMP 1.0, which was the initial submission, is not compatible with CAMP 1.1 (backward or forward, for the client side or the provider side).



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)