OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

camp message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


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


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

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

If we were to say that no version of CAMP is necessarily backwards compatible with any previous version of CAMP and that all version negotiation should be done through platform_endpoints->platform_endpoint then it doesn't matter what we call the next edition of CAMP as long as it is not "CAMP 1.1" (although, to avoid confusion, it should probably be some number greater than "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)


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]