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

[Gabor Maghera]

>
> So, I'm also keen to see what the preferred and most efficient approach
> is, and if they are the same or mutually exclusive.  The branching
> approach makes sense to me, but it does not seem to fit within the
> Perforce methodology from what I have seen.  The Perforce docs even say
> that they based their branching model on the ancient method of making a
> physical copy.  I'd like something that is not a hark back to the 80's
> when source trees were measured in kilobytes.


Perforce is one of the more efficient SCM systems at branching, and I do
believe that branching fits their model.  I am accustomed to the model Rick
describes.  You can see the history of your code at a glance as far as
releases go, just like the Subversion example you showed.

In Perforce branches are created using lazy-copying.  The server only keeps
track of changes for modifications on a child branch, except for binary
files.  It does not store additional copies for branches.

Cheers,
Gabor

On Jan 3, 2008 7:02 PM, Rick Macdonald <rickmacd at shaw.ca> wrote:

> 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...
>  _______________________________________________
> perforce-user mailing list  -  perforce-user at perforce.com
> http://maillist.perforce.com/mailman/listinfo/perforce-user
>