Tags/branches with Subversion, Best Practices?

  I've got CC building our SVN trunk continuously, but I'd like to also have 
it build like an "integration" tag/branch which only includes things our 
release coordinator has approved.

My thought is that different revisions could be "copied" (merged?) into a 
specific tag, and have CC be building that one as well. Does anyone have a 
better pattern?

Another question is whether there's any way to have CC "reuse" project 
definitions. I really don't want to have to maintain two set of projects with 
the only difference being the SVN path.

I freely admit I'm both a CC and SVN newb - the person responsible for this 
left the project a while back, and I'm picking up from scratch - so if I'm 
missing the obvious, please set me straight.

Thanks,
Doug

------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first