OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

oslc-ccm message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

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

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

Nick Crossley commented on OSLCCCM-14:

There are valid use cases for both deleting or archiving entire components (the container of all baselines and streams of that component), as well as use cases for deleting or archiving individual baselines and streams. Not all baselines are equally important. Consider a series of baselines produced by a continuous build process - the great majority of such baselines cease to be of much interest after they have been supplanted by more recent ones. Some baselines will be more interesting because they have been selected for further testing, or for release. In many systems, a baseline has a non-zero cost to preserve it - some storage cost, cost in UI complexity, etc. Users want to delete or at least hide obsolete baselines.
The suggested non-normative text is not incompatible with the idea that a user might be able to change the provenance history using other mechanisms; the spec will not contain any suggestion that the server modify the provenance chain automatically.

> 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

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]