[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Commented: (CAMP-146) campVersion limits future compability
[ http://tools.oasis-open.org/issues/browse/CAMP-146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=35895#action_35895 ]
Anish Karmarkar commented on CAMP-146:
--------------------------------------
My thinking here is that a particular artifact is designed to work with a specific version (1.1 or 2.0 or whatever). It uses specific features of that spec. A provider that process such an artifact must support that particular version or a version that is compatible with it or a version that support everything that is in the artifact as defined by the campVersion value. I imagine that every CAMP spec (1.1 and future) will specify its backward compatibility with other past versions of CAMP specs.
IMHO I don't think we need to change anything here.
> 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
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]