[p4] Automatic lock in checkout (edit)

Javier Crespo javier.crespo at altana.es
Mon May 14 11:17:56 PDT 2007


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.










More information about the perforce-user mailing list