[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Organization Advise

From: Brad Rhoads <brhoads_at_zethcon.com>
Date: 2004-05-28 23:42:56 CEST

Hi Everyone,

I'm just getting started with subversion and would like some advise on how
to best organize our repository. We have a fairly complex system consisting
of the following:

1. Desktop app written in Delphi
2. Background processes (~ 7 different executables) written in C
3. Terminal based application written in C
4. Web interface written in Java/JSP
5. All of the above access an Oracle database. We script everything. There
are some procs and tables that are only used by 1 of the above, but most are
used by all.

I would like to be able to easily tag 1-5 as release x.x. But I don't want
every developer to have to have working copies of all everything. Plus we
are always doing bug fixes and installing patches for individual clients. So
we need a good way to keep track of exactly which version each client is
running. What's the best way to organize our repository in terms of projects
based on these requirements? One big project vs. several projects? How do we
deal with the SQL as it is functionally related to other parts of the

Thank you very much for your advise.

Brad Rhoads
Zethcon Corporation
847-318-0800 x 53

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri May 28 23:43:26 2004

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.