[OASIS Issue Tracker] (OSLCCCM-36) Need to distinguish in-progress change set from delivered/committed one

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

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

Nick Crossley commented on OSLCCCM-36:
--------------------------------------

What if a server allowed a change set to be delivered independently to more than one stream?
Rather than a committed flag or link on a change set, what about having zero or many includesChangeSet links from a stream to change sets? Those links would also be copied to baselines, which might be nice for reporting.
This approach would require an OSLC client to use a query to find out if a given change set had or had not been delivered anywhere .

However, the above ties the concept of a committed or immutable change set to the concept of a delivered change set. The two could be different: a server could support committing / completing a change set before delivering it anywhere. Also, relying on just the references from includeChangeSet could cause a previously immutable change set to become mutable if the streams and baselines to which it had been delivered were deleted.

Should we just un-deprecate oslc_config:mutable? As well as adding oslc_config:committed as an optional property on change sets? As well as adding oslc_config:includesChangeSet as an optional multi-valued property on streams and baselines?

> Need to distinguish in-progress change set from delivered/committed one
> -----------------------------------------------------------------------
>
>                 Key: OSLCCCM-36
>                 URL: https://issues.oasis-open.org/browse/OSLCCCM-36
>             Project: OASIS OSLC Lifecycle Integration for Change and Configuration Management (OSLC CCM) TC
>          Issue Type: Improvement
>          Components: Configuration Management
>            Reporter: David Honey
>            Assignee: Nick Crossley
>
> The current change management spec describes the resource shape for a oslc_config:ChangeSet. We have a requirement to distinguish an in-progress change set from a delivered/committed change set. We have been using the deprecated oslc_config:mutable property. A value of "false"^^xsd:boolean meant in-progress, and "true"^^xsd:boolean meant delivered. However, this usage is a little obscure and not documented for in the spec for this specific use case.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)