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

[Ivey, William]

> 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.

It's even faster when you have both branches resident on the
machine all the time. In fact, you can build both at once,
tools permitting. (I usually have four or five branches of our
product synced at one time since I have to work on and build
all the currently supported versions. Changing the "identity"
of a single directory would be a nightmare.)

It's a one time expense in terms of time, and disk space is
cheap.

You can "fake it" to make what you're used to happen by playing
games with your client mapping or with symbolic links if you're
using a Unix system, but it's not as safe and convenient as
one directory per branch.

-Wm




-----Original Message-----
From: perforce-user-bounces at perforce.com
[mailto:perforce-user-bounces at perforce.com] On Behalf Of Steve Williams
Sent: Thursday, January 03, 2008 7:59 PM
To: Perforce Users
Subject: Re: [p4] How do YOU identify the code set for a release?

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.

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.

-- 
Sly

Shawn Hladky wrote:
> >>Perforce branching seems to require a physical copy on the
> >>client disk of the whole source tree for the branch.
> use the -v switch to prevent this.
>  
> >>the requirement to fill out a text-based form to make a
> >>simple branch makes scripting the process an interesting exercise in
> >>text file manipulation.
> use P4Perl, P4Ruby, P4Python, P4.Net , P4COM, or one of the other APIs

> and this is a piece of cake.
>



This message and its attachments may contain legally privileged or
confidential information. This message is intended for the use of the
individual or entity to which it is addressed. If you are not the
addressee indicated in this message, or the employee or agent
responsible for delivering the message to the intended recipient, you
may not copy or deliver this message or its attachments to anyone.
Rather, you should permanently delete this message and its attachments
and kindly notify the sender by reply e-mail. Any content of this
message and its attachments, which does not relate to the official
business of the sending company must be taken not to have been sent or
endorsed by the sending company or any of its related entities. No
warranty is made that the e-mail or attachment(s) are free from computer
virus or other defect.
_______________________________________________
perforce-user mailing list  -  perforce-user at perforce.com
http://maillist.perforce.com/mailman/listinfo/perforce-user