[OASIS Issue Tracker] Issue Comment Edited: (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=36435#action_36435 ] 

Martin Chapman  edited comment on CAMP-146 at 2/10/14 2:55 PM:
---------------------------------------------------------------

from 5th Feb 2014:

      MOTION: close #146 w no action (Alex/Anish)
      Approved w/o

      was (Author: martin.chapman):
    from 4th Feb 2014:

      MOTION: close #146 w no action (Alex/Anish)
      Approved w/o
  
> 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
>          Components: Spec
>            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