9 messages in com.perforce.perforce-user[p4] Enforcing "code chill"
FromSent OnAttachments
Jim Crossley24 Oct 2003 08:47 
Todd Short24 Oct 2003 09:13 
Dave Lewis24 Oct 2003 09:23 
Jim Crossley24 Oct 2003 09:46 
Stephen Vance24 Oct 2003 16:03 
Jim Crossley24 Oct 2003 17:01 
Jeff Bowles06 Nov 2003 20:24 
Chuck Karish07 Nov 2003 06:40 
Stephen Vance07 Nov 2003 10:23 
Subject:[p4] Enforcing "code chill"
From:Stephen Vance (ste@vance.com)
Date:10/24/2003 04:03:38 PM
List:com.perforce.perforce-user

Jim --

I would recommend release branching and keeping the protections tight on the depot directory tree that contains release branches instead of changing the policy of the codeline. Take a look at the best practices white paper on the Perforce web site.

Steve

At 11:48 AM 10/24/2003, Jim Crossley wrote:

I'm hoping someone can suggest a way I can achieve the following with Perforce without using jobs, if at all possible.

I want to mark a particular codeline as being in "code chill" so that only approved fixes are allowed to be submitted. More specifically, I want the submit to fail (hopefully with a useful error message) if the submitter doesn't include text in his change description that matches a particular regular expression, e.g. "CR #[0-9]+". I wouldn't expect the "code chill" to last more than a few days, so I would want to be able to easily toggle the restriction.

Any ideas?

Thanks, Jim

_______________________________________________ perforce-user mailing list - perforce-user at perforce.com http://maillist.perforce.com/mailman/listinfo/perforce-user

Stephen Vance mailto:steve at vance.com http://www.vance.com/