Yes, those links are not part of SCM 1.0, and that is deliberate! I agree we need to consider them in the future, but it is non-trivial - different SCM systems have very different versioning models - consider Subversion, for example. Fortunately, the predecessor/successor links are not required for the initial drill-down and code review scenarios for SCM 1.0.
Nick.
To: [email protected]
From: Frank Schophuizen <[email protected]>
Sent by: [email protected]
Date: 05/14/2010 05:19AM
Subject: [oslc-scm] Predecssor/successor misisng from spec v1.0
Hello,
I was reading through SCM Specification v1.0 and I noticed that there is nothing specified about successors or predecessors.
Given that SCM is about (managing) the evolution of software configurations, I would expect (at least some basic) concept of predecessor/successor, at object version level or at configuration level.
More specifically, a baseline consists of configurations, consisting of object versions from change sets. The first configuration consists of a baseline without change sets. The next configuration consists of a baseline + change set(s). Then the next configuration, does it consist of the previous configuration + change set(s). But does a change set contain the changes relative to a baseline or relative to the (or "a") previous configuration? Which configuration is the "previous" configuration?
In other words, we need a concept of a "stream", a sequence of configurations that represents the (sequential) evolution of the software. And we need a concept of "integration" to merge configurations of different streams, and a concept of "branching" to evolve a configuration in different directions. One of the most common cases of branching is maintenance (bugfixing) of old releases while continuing development for a new release. A common case for "integration" is component development; various components are developed independently (i.e. in independent streams) and then integrated (i.e. used or reused) in other streams to compose a product or system. Even various different products or systems may be developed (in independent streams) using/reusing components from a component library, developed in independent streams too.
I can imagine that these streaming concepts are not for V1.0 of the SCM spec, but shouldn't we at least have a concept of predecessor/successor in V1.0 of the spec?
Regards,
Frank.
--
TOPIC Embedded Systems
P.O. box 440, NL-5680 AK Best
Netherlands
Phone (+31) 499 336979
Fax (+31) 499 336970
_______________________________________________
Oslc-Scm mailing list
[email protected]
http://open-services.net/mailman/listinfo/oslc-scm_open-services.net
