RE: [alf-dev] RE: ALF SCM Vocabulary - Data Model version5+firstpassa sc

["Tim Buss" <TBuss@xxxxxxxxxx>]

Vinay,

The "data model" description is not supposed to be a full description of
the relationships of the object within the SCM - we are not trying to
build one - but rather describe what might be seen externally that might
be useful in the context of ALF.  Thus Baseline and Changeset are both
Version Collections since it is convenient to re-use the same structure
defintion. 

In our vocabulary discussion today, the consensus was that it is more
likely that relationships between Changesets and Baselines are known
outside the SCM and that while it may be useful for an SCM to provide
operations that relate them, it did not seem to be a common use case.

So I guess the question for you is how you would see this being used. Do
you have a use case that would require a formal relationship between
Changeset and Baseline that would necessarily be provided by the SCM? If
so does this need to be expressed in the exposed data structures or is
it sufficient for the SCM to provide operations that would, say, return
the set of changesets associated with a particular baseline etc.

regards
Tim 

-----Original Message-----
From: alf-dev-bounces@xxxxxxxxxxx [mailto:alf-dev-bounces@xxxxxxxxxxx]
On Behalf Of Slava Imeshev
Sent: Wednesday, July 12, 2006 10:22 AM
To: ALF Developer Mailing List
Subject: Re: [alf-dev] RE: ALF SCM Vocabulary - Data Model
version5+firstpassa schema types

Eric,

I agree with what you say. But for some VCS systems a baseline is a
state of the system at the given Changeset number. And yes, that would
include all change sets related to the depot view spec. For such systems
versions of elements themselves may not be of great value because
syncing is done to a changeset.

Slava

----- Original Message -----
From: "Eric Minick" <etm@xxxxxxxxxxxxx>
To: "ALF Developer Mailing List" <alf-dev@xxxxxxxxxxx>
Sent: Wednesday, July 12, 2006 9:47 AM
Subject: Re: [alf-dev] RE: ALF SCM Vocabulary - Data Model version
5+firstpassa schema types


> I'm not sure that makes much sense. A baseline is going to capture a 
> snapshot of the versions in a configuration at a moment in time. From 
> the wiki: "A baseline is therefore a fixed set of versions, one
version 
> per element in a component". At it's most basic level, you are
applying 
> a label to some project.
> 
> The Change-set is also a collection of versions but it is a much
smaller 
> set with a different purpose. This might be the collection that is 
> submitted as part of an atomic check-in, the versions that make up a
bug 
> fix, or some other relatively small collection.
> 
> For a Baseline to be represented as a collection of Changesets, it
would 
> have to include every change-set leading to that baseline in the
history 
> of the project. Or, more likely, a previous baseline and the set of 
> changesets that differentiates the two.
> 
> I think partial change sets could be a possibility (a bug is half
fixed 
> when a baseline is completed) but that's more of a social problem than
a 
> technical one.
> 
> Cheers,
> Eric
> 
> Slava Imeshev wrote:
> 
> >I'd think that a Baseline were a set of ChangeSets then. Otherwise
this 
> >structure may create possibility of having a baseline consisting of
"partial 
> >change sets"...
> >
> >Regards,
> >
> >Slava Imeshev
> >vimeshev@xxxxxxxxxxxx
> >
> >  
> >
> 
> _______________________________________________
> alf-dev mailing list
> alf-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/alf-dev
_______________________________________________
alf-dev mailing list
alf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/alf-dev

**********************************************************************
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.