Uploaded image for project: 'OASIS OSLC Lifecycle Integration for Change and Configuration Management (OSLC CCM) TC'
  1. OASIS OSLC Lifecycle Integration for Change and Configuration Management (OSLC CCM) TC
  2. OSLCCCM-24

Moving ChangeRequest properties to subclasses could create incompatibilities

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Component/s: Change Management
    • Labels:
      None
    • Proposal:
      Hide

      CM 3.0 should put tracksRequirement and implementsRequirement back on ChangeRequest to maintain CM 2.0 compatibility and to recognize that these properties could apply to any subClassOf ChangeRequest, not just ReviewTask and Enhancement.

      That would result in no new properties on any of the subclasses of ChangeRequest in CM 3.0, all the properties would be inherited from ChangeRequest. That's probably ok because 1) new properties could be added by servers or new versions of the specification, and 2) the subclasses are still useful for different behaviors, lifecycle state machines, etc.

      Show
      CM 3.0 should put tracksRequirement and implementsRequirement back on ChangeRequest to maintain CM 2.0 compatibility and to recognize that these properties could apply to any subClassOf ChangeRequest, not just ReviewTask and Enhancement. That would result in no new properties on any of the subclasses of ChangeRequest in CM 3.0, all the properties would be inherited from ChangeRequest. That's probably ok because 1) new properties could be added by servers or new versions of the specification, and 2) the subclasses are still useful for different behaviors, lifecycle state machines, etc.

      Description

      CM 2.0 only defined oslc_cm:ChangeRequest and all the CM properties were properties of that class.

      CM 3.0 introduces a standard set of subclasses of ChangeRequest including Defect, Enhancement, ReviewTask and Task.

      Currently the CM 3.0 spec moves ChangeRequest property tracksRequirement to ReviewTask and implementsRequirement to Enhancement. This could be a breaking change if CM 2.0 clients no longer see these properties on a ChangeRequest.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              jamsden James Amsden
            • Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: