Re: Repository management

> If no code gets copied back and forth between projects, then you're
> probably better off with one repository per project. If a project uses
> a library that's stored in another repository, you can use the
> svn:externals property to automatically bring the library code into
> working copies of the project.

That's what we're assuming we're going to do at this point, since in the
vast majority of cases the libraries are DLLs that are used by the other
projects, not source to be included directly.

> As far as hook scripts go, one thing you might want to consider is
> integration with your issue tracking system.

We are currently using a system called TeamTrack, from an outfit called
Serena Sofware, or something like that, and I'm unsure whether or not it has
any integration capabilities. That's a good point, though, and I'll be sure
to bring it up.

> P.S. If you'll excuse a bit of self-promotion,

Not a bit, thanks.

> I have a book coming out in a few weeks that goes into much greater
> detail on exactly the things you seem to be interested in. I talk a
> lot about repository layouts, hook scripts, and other
> Subversion--Development Process integration.

I'll definitely keep that one in mind, thanks. In fact, I've forwarded that
link to our network admin and configuration manager guys.

Thanks for your input.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Apr 25 17:55:28 2005