On Mon, Aug 25, 2008 at 6:12 PM, Fred Larsen <[EMAIL PROTECTED]> wrote: > I need some help coming up with the best branching scheme for a multi > developer web application. This application will have frequent releases, > maybe weekly. I really want to minimize the repository maintenance with > merging changes to multiple branches.
Using the SVK client with SVN repos solves most of the branching/merging problems. It also allows each developer to maintain a mirror (depot) and check out/in from the mirror while coding, testing, etc, without pushing broken code back to the main repo. Then, when their code is ready, it can be pushed back to the main repository. Each developer can maintain several branches and tags in their own personal mirror without muddying up the main repo. SVK is a 100% compatible SVN client. Some users can use SVK as their client, while others use the regular SVN clieny. The only way to tell the difference is by how disgruntled the regular SVN users are... And the best part is that SVK doesn't scatter .svn folders all over your working copy :) Getting started with SVK: http://spf13.com/feature/using-svk-increase-productivity justin -- http://justinhileman.com _______________________________________________ UPHPU mailing list [email protected] http://uphpu.org/mailman/listinfo/uphpu IRC: #uphpu on irc.freenode.net
