[p4] How do YOU identify the code set for a release?

[todd.benham@kodak.com]

When I was testing labels (without scripts), I was able to do something
like this:
p4 tag -l V01.00.00 //depot/MAIN/source

Or this for partial set of directories:
p4 tag -l V01.00.00 //depot/MAIN/source/Common*/...
//sdepot/MAIN/source/proj1*/...



Todd 


-----Original Message-----
From: perforce-user-bounces at perforce.com
[mailto:perforce-user-bounces at perforce.com] On Behalf Of Shawn Hladky

>
> So option #1 is to use a label.  Coming from years of CVS use, this is 
> what I naturally gravitated to.  I was a little surprised that 
> creating a label is so cumbersome; e.g. it involves filling out a 
> form.  But I created a small script to turn it back into a one-liner 
> similar to what one does in CVS.
>
> I know there are both 'static' and 'automatic' labels; let's assume we 
> would only ever care to release at a changelist, so we use only 
> automatic labels where the Revision: field is a changelist number.  My 
> script essentially takes the label string and a changelist number, 
> then creates and submits the appropriate form.
>
> One downside of this approach that I've found is that p4v makes 
> working with labels fairly cumbersome: by default, you see labels 
> created by you.  My script actually creates them as a "build" user, so 
> you have to go and manually type in "build" each time to find the 
> labels.  And then you see *all* labels across the whole depot, which 
> is not as nice as "cvs stat -v Makefile" to find all the labels 
> associated with a given project in the depot.
>