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

[Rick Macdonald]

Steve Williams wrote:
> Sure, you can make the branch directly on the server using the -v 
> switch, but it's useless without having the branched source tree on your 
> local drive.  It's effectively the same as copying the tens of gigabytes 
> on the local disk, except you're pulling it over the network.  With 
> Subversion, I can create the branch then switch my local working copy 
> from trunk to the branch in just a few seconds, do the build, then 
> switch back to the trunk.
>   
I was wondering how you were going to build it if it wasn't on disk...

If a sync of 10's of gigabytes of source code takes half an hour, 
doesn't the build run until the next day anyway?

> Having to learn Perl, Python or Ruby, or coding a tool using the P4 API 
> to automate what should be a simple branching process is just a little 
> over the top.
>   

I did it in a csh script once with this:

p4 change -o | sed "s~<enter description here>~Creating release branch 
$relnum.~1"| p4 submit -i

Are you looking for help to dissuade the change to Perforce, or for help 
in streamlining the process using Perforce?

...RickM...