[p4] How many of you use a sandbox area for user items.

[Christopher Corbell]

We have a more broadly defined //Sandbox depot.  Sandbox is used both  
for individual and team prototypes, and for unstable project work  
(which is promoted to another depot/branch when it's stable).

Teams that are adding incremental functionality usually only need to  
use the team sandbox area for major refactoring that may destabilize  
the product; in normal construction they work directly in the "dev"  
branch (the nightly build branch of the production depot, which is  
required to be buildable and pass unit tests).  On the other hand  
teams working on new systems often work in sandbox for their daily  
construction and only promote to dev when stable milestones are  
achieved.  Their are higher layers of source promotion as well - code  
is promoted from dev to main for QA drops, and from main to release  
for product releases.

It works pretty well as long as integrations only go one way.  It can  
get very confusing if there's concurrent work on the same project  
going on in sandbox and dev, but that's true of separate branch work  
in general.

User-specific sandboxes for investigations/prototypes are fairly  
common for our more ambitious engineers.  Their isn't a lot of p4- 
protect-enforced limitation on engineering users - they can branch  
existing projects into their personal sandboxes and promote changes  
back, etc.

- Chris

On May 8, 2006, at 6:16 PM, Brian Colfer wrote:

> List,   do you use a sandbox ... or other area defined for user  
> specific
> items?
>
> That is besides ... you Stephen P.
>
>
>
>
>
> - Brian
>
>
>
>
>
> ==========================
>
> Brian Colfer
>
>
>
> briancolfer at comcast.net
>
>
>
> MS  IM: briancolfer at hotmail.com
>
> Yahoo IM: briancolfer at yahoo.com
>
> Google Talk: brian.colfer at gmail.com
>
>
>
>
>
> _______________________________________________
> perforce-user mailing list  -  perforce-user at perforce.com
> http://maillist.perforce.com/mailman/listinfo/perforce-user