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

[Jamie.Echlin@barclayscapital.com]

The key point is that there is no obvious equivalent of svn switch in
perforce... Yes you can branch on the server with -v but as Steve said
you can't work on it unless you get it on the disk, so you're going to
have to do the disk copy one way or another. Probably svn switch could
be done with some view spec manipulation and sync -k...

But the way we addressed this problem of branching very large codebases
is to come up with a custom tool that implemented a form of sparse
branching, which we call shelving. Only those files that are different
from the "trunk" are actually branched (a la clearcase)... This makes
the branch useless in of itself, you can only work on the files after
unshelving... At which point you can commit (deliver the branch) or
reshelve again...

Cheers, jamie



> -----Original Message-----
> From: perforce-user-bounces at perforce.com 
> [mailto:perforce-user-bounces at perforce.com] On Behalf Of 
> Steve Williams
> Sent: 04 January 2008 04:08
> To: Perforce Users
> Subject: Re: [p4] How do YOU identify the code set for a release?
> 
> 
> 
> Rick Macdonald wrote:
> > 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?
> >   
> 
> The tens of gigabytes includes game data files as well as 
> source code.  
> The build itself generally takes around an hour or two.
> 
> 
> > 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?
> >
> >   
> 
> I'm still learning a lot about Perforce, so this thread has 
> actually been useful in many respects.  The pool of Perforce 
> knowledge in the company is quite limited, so I'm still 
> trying to learn "the Perforce way" of working.
> 
> --
> Sly
> 
> 
> 
> 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
> 
------------------------------------------------------------------------
For important statutory and regulatory disclosures and more information about Barclays Capital, please visit our web site at http://www.barcap.com.

Internet communications are not secure and therefore the Barclays Group does not accept legal responsibility for the contents of this message.  Although the Barclays Group operates anti-virus programmes, it does not accept responsibility for any damage whatsoever that is caused by viruses being passed.  Any views or opinions presented are solely those of the author and do not necessarily represent those of the Barclays Group.  Replies to this email may be monitored by the Barclays Group for operational or business reasons.

Barclays Capital is the investment banking division of Barclays Bank PLC, a company registered in England (number 1026167) with its registered office at 1 Churchill Place, London, E14 5HP. This email may relate to or be sent from other members of the Barclays Group.
------------------------------------------------------------------------