RE: [alf-dev] RE: ALF Source Code Mangement Vocabulary Meeting meetingmi

["Adam Simantel" <ASimantel@xxxxxxxxxx>]

Dear ALF SCM Vocabulary team,

I like the Build use cases that Eric has drafted.  Some questions and
thoughts:

Regarding the use case "Get new versions since" -- Is this a request for
the versioning provider to answer the question:  "Should we build
again?"  Or, does it actually get files?  Or, both?  Perhaps "Update a
workspace" is used to get files, and "Get new versions since" is really
the decision maker, answering the question "Is it time to build again?"
I'm trying to better distinguish "Update a workspace" and "Get new
versions since".

Would a continuous integration build system like to subscribe to ALF
events that can tell it when changes have occurred to certain streams?
It could listen to "check-in" or "promote" or "change-set promotion"
events on a stream.  This may introduce other use cases.  (I haven't
proposed any).

And, I've added two additional use cases, identified as [proposed for
discussion], #7 and #8, which hopefully we can touch on at this morning
meeting.
	http://wiki.eclipse.org/index.php/ALF/Build_Server_Use_Case

Regards,

Adam Simantel
Serena Software


-----Original Message-----
From: alf-dev-bounces@xxxxxxxxxxx [mailto:alf-dev-bounces@xxxxxxxxxxx]
On Behalf Of Eric Minick
Sent: Tuesday, May 16, 2006 3:16 PM
To: ALF Developer Mailing List
Subject: Re: [alf-dev] RE: ALF Source Code Mangement Vocabulary Meeting
meetingminutes

SCM Vocab Team and all,

I've put together a quick overview of the SCM integration use cases from

the perspective of build management tools. Comments and suggestions from

those who are familar with these tools would be most welcome.

It's currently up on the wiki here: 
http://wiki.eclipse.org/index.php/ALF/Build_Server_Use_Case .

As we discussed, this is a fairly coarse grained set of use cases. On 
further reflection though, I'm not sure that's the right direction. As 
we move have added more customizable workflow oriented behavior in our 
commercial app, we found it helpful to expose more low level and scm 
dependent concepts directly to the user - particularly the advanced 
user. In the open source tool, the coarse grained approach does simplify

development.

In a tool like ALF that is primarily geared towards users scripting 
interactions in service flows, finer grained use cases might be more 
appropriate, if only in the context of the more coarse.

Cheers,

Eric Minick
Urbancode, Inc.
_______________________________________________
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.