-----Original Message----- From: Brian Silverman [mailto:bsilverman at lanexllc.com] Sent: Tuesday, February 13, 2001 8:16 AM To: perforce-user at perforce.com Subject: [p4] Codelines

I'm confused on the best way to arrange codelines. There's two opposing issues that confuse me. The High Level SCM Best Practices document suggests "check-in often", and "Stay in sync with the codeline". They also suggest some sensible code-lines, below:

Some sensible codeline policies: Development codeline: interim code changes may be checked in; affected components must be buildable. Release codeline: software must build and pass regression tests before check-in; check-ins limited to bug fixes; no new features or functionality may be checked in; after check-in, branch is frozen until entire QA cycle is completed. Mainline: all components must compile and link, and pass regression tests; completed, tested new features may be checked in.

Well, I don't want to *work* in the development codeline, because I'd be afraid that other people's bugs are going to screw up my build. Or, if I do work in the development codeline, I at least won't want to stay in sync with it, for fear that new syncs will bring in new bugs. And, if I work in the mainline, I won't be able to check-in often (without breaking policy).

So where do I work?

---- Brian Silverman Lanex, LLC bsilverman at lanexllc.com