[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=59317#comment-59317 ] 

Gilbert Pilz commented on CAMP-182:
-----------------------------------

If we reject the notion that all version negotiation must be done through platform_endpoints->platform_endpoint then we have a constraint-precedent problem to work out between this issue and CAMP-176.

If we accept the current proposal for CAMP-176 then the "next edition" of CAMP will not be backwards compatible with CAMP 1.1 and should probably be named something like "CAMP 2.0" (on the assumption that we use the major number increment to indicate this non-backwards-compatibility).

On the other hand, if we decide the the "next edition" of CAMP must be backwards compatible with CAMP 1.1 (and should therefore be called something like "CAMP 1.2") then the current proposal for CAMP-176 is unacceptable.

Rather than get lost in all these details I think we should decide whether the next edition of CAMP does or does not need to be backwards compatible with CAMP 1.1.

> 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)