[OASIS Issue Tracker] Commented: (CAMP-146) campVersion limits future compability

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

    [ http://tools.oasis-open.org/issues/browse/CAMP-146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=35237#action_35237 ] 

Alex Heneveld commented on CAMP-146:
------------------------------------

I think this is one of those things that will come back to bite us if we leave it (preventing multi-version compatibility).  OTOH it is fairly easy to resolve now.

I suggest:

* we make the field optional, with the proviso that:

If this field is not supplied, the Provider SHALL attempt to process the Plan.  In such case the Consumer is responsible for ensuring that the CAMP server is at the correct version.

* and either we weaken the normative language to say something like the following (allowing other values, such as ranges, to be introduced in the future):

The value MAY be "CAMP 1.1" (the Specification Version as per section 1.8), and such a value will indicate that the Plan is designed against this version of the Specification.

* or we introduce a range notation

The value SHALL be a range of the form described in XXX.  For example [1.1] to indicate this Plan has a hard dependency on this exact CAMP Specification Version.

(Maven range notation is the best I've found - http://docs.codehaus.org/display/MAVEN/Dependency+Mediation+and+Conflict+Resolution#DependencyMediationandConflictResolution-DependencyVersionRanges )

> campVersion limits future compability
> -------------------------------------
>
>                 Key: CAMP-146
>                 URL: http://tools.oasis-open.org/issues/browse/CAMP-146
>             Project: OASIS Cloud Application Management for Platforms (CAMP) TC
>          Issue Type: Improvement
>            Reporter: Alex Heneveld
>
> The campVersion of the YAML requires a single "Specification Version" string to be supplied.  To conform with 1.1 it MUST say 1.1.
> This will make it hard in future for a plan to indicate it runs on 1.1 (old platforms) AND 1.2 (new platforms).
> If this were a numeric range String a la Maven (e.g. "[1.1,1.2]") or even a list it would be nicer.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira