[OASIS Issue Tracker] (OSLCPROMCO-3) Define change management scenario and model to be used in PROMCODE spec

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

    [ https://tools.oasis-open.org/issues/browse/OSLCPROMCO-3?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=37238#comment-37238 ] 

Masaki Wakao commented on OSLCPROMCO-3:
---------------------------------------

References: 
Tracked Resource Set (TRS) specification: http://open-services.net/wiki/core/TrackedResourceSet-2.0/
OASIS OSLC Configuration Management TC: https://wiki.oasis-open.org/oslc-ccm/


> Define change management scenario and model to be used in PROMCODE spec
> -----------------------------------------------------------------------
>
>                 Key: OSLCPROMCO-3
>                 URL: https://tools.oasis-open.org/issues/browse/OSLCPROMCO-3
>             Project: OASIS OSLC Lifecycle Integration for Project Management of Contracted Delivery
>          Issue Type: Improvement
>            Reporter: Masaki Wakao
>
> There are 2 different level of scenarios raised during meeting on April, 22.
> - Simple change log
> - Transactional change (baseline, change-set)
> We have to define our scenario and model for PROMCODE.
> There are candidate external definitions for each scenario:
> - TRS for simple change log
> - Configuration Management for transactional change



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