[p4] Workspace option: exclusive open

[Shawn Hladky]

>>If you're workspace can only see one branch, how do you integrate
>>between release branches?
Your workspace only needs to include the destination of the integration.

I don't know that I'd go so far as to say that one workspace per branch is a

best practice, but it is certainly a common practice.  Personally I use lots

of workspaces, some of them scoped to one branch, some covering many
branches.

Most of our developers use just one workspace, and they sometimes
accidentaly
check code into the wrong branch.  I don't think one workspace per branch
would
reduce or increase that problem.  Humans make mistakes, and I don't really
think
one approach is any more error-prone than the other.  They just cater to
different styles
of working.

On 9/14/07, Ivey, William <william_ivey at bmc.com> wrote:
>
> If you're workspace can only see one branch, how do you integrate
>
> between release branches? (I can't see this being a best practice if
>
> it doesn't work - and, by the way, I got the idea from Perforce's own
>
> documentation.)
>
>
>
> If I have two workspaces and change directories, but forget to change
>
> workspaces (and P4CONFIG doesn't work with the GUI) then I might
>
> not submit a file into the wrong branch - but I will create a useless
>
> change on the wrong branch, and fail to update the branch I intended.
>
>
>
> Whereas if I have one workspace that maps multiple server branches
>
> to multiple directories on my system, changing directories is all I need
>
> to do and everything will go as intended. Perforce automatically directs
>
> the command to the right branch based on my local directory path no
>
> matter what client I happen to use. That's part of its design and I
> don't
>
> see any easy way to create the problem you describe by doing it this
>
> way.
>
>
>
> I think you are misinterpreting the term "workspace" (replace it with
>
> "client" and maybe my meaning will be clearer). I'm certainly not
>
> talking about mixing file from multiple branches in a single directory
>
> on my system.
>
>
>
> -Wm
>
>
>
>
>
> ________________________________
>
> From: Gabor Maghera [mailto:gmaghera at gmail.com]
> Sent: Friday, September 14, 2007 3:35 PM
> To: Ivey, William
> Cc: Rick Macdonald; perforce-user at perforce.com
> Subject: Re: [p4] Workspace option: exclusive open
>
>
>
> It may not be as efficient to set up a dedicated workspace for each
> codeline, but it is a safety guard and a best practice.  This is
> especially important for release codelines but it also helps with
> development codelines.  The idea is to reduce the likelihood of someone
> checking code into an inappropriate branch and therefore destabilizing
> it.
>
> _______________________________________________
> perforce-user mailing list  -  perforce-user at perforce.com
> http://maillist.perforce.com/mailman/listinfo/perforce-user
>