Suggested structure?
From: Gerald Britton <gerald.britton_at_gmail.com>
Date: Tue, 18 Oct 2011 06:25:05 -0700 (PDT)
I am implementing a repository for a development group at my office. The devs all work from a common set of templates in SQL, VB, and Visual Studio. These are used for a series of mini-projects. I'm thinking of something like:
---- Master
The idea is, that development happens under Dev for new projects and modifications of existing projects. When a project is ready, it is promoted to production and either copied (if new) or merged (if a modification) to Prod. Decommissioned work is moved to Arch to maintain consistent historical records.
Each developer will maintain a working copy of Master, but does not need all the files in Prod, Dev, or Arch. usually, a dev will only need the project files in Prod (if working on a mod) and Dev (both for new projects and mods).
This raises an issue in that when a dev checks out Master, he wants the directory structure but only those projects he's working on under Prod and Dev.
For modifications, a dev would branch the project under Prod to Dev, do the development/test/debug cycle, then merge the changes back to Prod at promotion time.
Normally a dev would not want anything under Arch, which would be maintained by an administrator (probably me!)
I'm looking for feedback on a couple of issues:
1. Does this setup make sense or what other structure should I look at?
2. With this structure, how can I keep the working copies small so that no developer needs all active projects in their WC?
------------------------------------------------------
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
|
This is an archived mail posted to the TortoiseSVN Users mailing list.
This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.