[OASIS Issue Tracker] (OSLCCCM-14) How should previousBaseline behave when an intermediate baseline is deleted?

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

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

James Amsden commented on OSLCCCM-14:
-------------------------------------

Deleting a baseline seems to contradict the meaning of baseline. So does any attempt by a server to modify the provenance/version history chain. Perhaps it is not individual baselines that should be archived, but rather the container/project area of all baselines. If a user wants to do something particular with specific baseline, then that might be best done by establishing a new provenance chain, indicating that the old chain is no longer important or needed and can be archived. Then users control breaks in the provenance chain, and servers don't try to guess something that might be reasonable when specific baselines are deleted.




> How should previousBaseline behave when an intermediate baseline is deleted?
> ----------------------------------------------------------------------------
>
>                 Key: OSLCCCM-14
>                 URL: https://issues.oasis-open.org/browse/OSLCCCM-14
>             Project: OASIS OSLC Lifecycle Integration for Change and Configuration Management (OSLC CCM) TC
>          Issue Type: Bug
>          Components: Configuration Management
>            Reporter: Nick Crossley
>            Assignee: Nick Crossley
>            Priority: Minor
>              Labels: work_required
>
> When a baseline is deleted, should existing baselines derived from the deleted one have their oslc_config:previousBaseline property updated to point to the previousBaseline of the one being deleted, to maintain the provenance chain? Or would this break things like digital signatures?



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