2 ms·
I've used a version control system that has this feature (Perforce, specifically). In principle, it's good. In practice, I think we found it to be more trouble
by shadowgovt 5y ago
I've used a version control system that has this feature (Perforce, specifically).
In principle, it's good. In practice, I think we found it to be more trouble than it's worth... Engineers go on break / vacation / get hit by a bus too often with the locks held, and then there has to be a policy process to break the lock while that user still has outstanding changes that are now stale (in an entire environment that didn't reconcile "stale" code well because it was designed to prevent the need to merge code).
At our scale, this required us to have someone act as a full-time "repo guru," which was a brutally thankless job.