[p4] Automatic lock in checkout (edit)

[David Weintraub]

I'm normally not a fan of a multiple branch scheme. If a build is bad,
insist that developers drop everything else until the build gets
fixed. By having a "stable" branch vs. a developer branch, you remove
the need for developers to fix their issues. After all, its your
branch that has the problem, not their branch. Also, they don't have
to worry if the code on their branch doesn't build because it doesn't
have to.

However, if you want to use a second branch, why not simply set the
protection table, so only certain developers (like just yourself or
maybe the development leads) have write permission to that branch. It
will save you the headache of keeping the files in that branch locked.
Plus, locking only prevents others from submitting a file while
someone else is modifying it.

On 5/14/07, Javier Crespo <javier.crespo at altana.es> wrote:
>
> Hi,
>
> (first of all sorry for my english)
>
>
> We are thinking in change the way we used Perforce.
>
> We want always have a stable-line that we can deliver at any moment,
> (for example now)
>
> We are thinking about to have only 2 brach, one for "deploy-line" and
> another for "stable-line".
> We want to make the changes in the "deploy-line".
> We want to compile with "stable-line" plus some fixes. If the build pass
> the test (of a human testing team), then we want to "integrate" that
> fixes into the "stable-line".
> In order to reduce risk (of dirty files), we want to lock the files
> (with the fix), and unlook it only when the file will be integrated.
>
>
> Is this a good way for have a "stable-line"?
> Do you know another way?
>
>
> Is there a way to make an automatic lock in checkout (edit)?
>
> Is there a way to keep the files locked after a checking (submit), and
> unlocked them when they are used in a integration?
>
>
> Thank you.
>
>
>
>
>
>
>
>
> _______________________________________________
> perforce-user mailing list  -  perforce-user at perforce.com
> http://maillist.perforce.com/mailman/listinfo/perforce-user
>


-- 
--
David Weintraub
qazwart at gmail.com