John,
Your config spec will branch your elements 1 by 1 as they are checked out.
There is no reason to create a branch on every element in the project, only
the ones that are being changed. I use the same config spec and I find it
works very well for me. ClearCase Details will allow you to see which
objects have had branches created. I produce that list before doing my
merges. I do do the merges 1 by 1. There may be an easier/better way but I
tend to be a little anal.
anne
> -----Original Message-----
> From: John Lawlor [SMTP:John@wbtsystems.com
> Sent: Thursday, February 03, 2000 10:57 AM
> To: cciug@Rational.Com
> Subject: [cciug] Branch for NT development
>
>
> Hi All,
>
> We are in the early stages of ClearCase and don't really use branches
> until
> now.
>
> One of the development groups wants to create a branch for doing NT
> development work only and then merge it back in a few weeks (another
> story).
> The development group each use their own views.
>
> What is the best way to manage this branch?. All I have come up with so
> far
> is,
> 1. Declare a branch type 'nt_development'
> 2. Do a Cleartool mkbranch nt_development.
>
> These raise a few questions,
> Can I branch the whole project or can I only do one file at a time?
> If I get the developers to setup the views with these rules:
> element * CHECKEDOUT
> element * /main/nt_development/LATEST
> element * /MAIN/1 -mkbranch nt_development
> that will branch each file version onto this branch, but will I have to
> merge the files back in 1 by 1?
>
> What is the best/smoothest way to get through this?
>
> All ideas are very very welcome.
>
> Regards,
>
> John.
>
> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
>
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
This archive was generated by hypermail 2b29 : Sun May 06 2001 - 00:22:58 EDT