RE: e-mail notification

So you are thinking that we would do something like:

<modificationset quietperiod="30">
        <clearcase viewpath="/view/wtdb2xmerge_mpkirby/vobs/psip/" 
recursive="true" 
branch="wtdb2xmerge">
             <property name="removeshadowedchanges" value="true"/>
        </clearcase>
</modificationset>


Perhaps I don't even need the "value=true" part.  

Mike

p.s. I'll be on vacation for the rest of the year, so lack of notes really does 
mean lack of 
progress :-)

On 12 Dec 2003 at 14:53, Jeffrey Fredrick wrote:

> 
> 
> Do you think doing this extra work is something worth including in the 
> current ClearCase 
> sourcecontrol plugin, w/the on/off controlled by an attribute? 
> ("removeshadowedchanges" or 
> something like that)
> 
> And you'll still need the custom email publisher, right? To send email to all 
> users of the branch? 
> And if I'm correct you'll also want to run with the attribute 
> skipusers="true" so that you don't send 
> email to people who changed the release but not the branch.
> 
> Jtf
> 
> -----Original Message-----
> From: cruisecontrol-user-admin@xxxxxxxxxxxxxxxxxxxxx 
> [mailto:cruisecontrol-user-
> admin@xxxxxxxxxxxxxxxxxxxxx] On Behalf Of Michael Kirby
>  <snip/>
> 
> It was brought to my attention that the clearcase subsystem currently figures 
> out whether the files 
> in a branch have changed using the cleartool lshistory -branch command
> 
> In our situation, our project branches are children of a parent "release" 
> branch. They 
> automatically inherit changes from the parent through the magic of the 
> .../LATEST label in 
> clearcase. 
> 
> In effect, we deliberately do not isolate our developers from changes made to 
> a release each 
> week. They are required to pull down (i.e. merge from the parent branch to 
> their working branch) 
> any changes that may conflict with what they are doing. This prevents private 
> branches from 
> going stale, and merging in lots of code that doesn't work, or wipes out 
> changes made by other 
> users.
> 
> As a consequence, just finding the files in the branch that have changed is 
> not good enough. I'll 
> have to subclass and change the ClearCase sourcecontrol method:
>     
>     public List getModifications(Date lastBuild, Date now)
> 
> So that it gets the changes from the current branch, changes in the parent 
> branch, and removes 
> any files occluded by the child branch. Any clearcase geniuses out there have 
> a better idea, I am 
> all ears.
> 

---
kirby@xxxxxxxxxxxxxxxx
To obtain my PGP public key, mail "SEND PUB KEY" in the 
subject to "kirby@xxxxxxxxxxxxxxxx"



-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click