On Mon, Aug 25, 2008 at 4: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. Also, I need to have a mechanism to > allow for code to be in a > state of testing while development continues. This way QA can be testing > without stopping development and vise versa.
You are describing the definition of a distributed revision control system. SVN is not one of them, but there's a client (svk) that's add distributed capabilities. I haven't used svk but such a fundamental change to the design of the RCS seems like could only be added in a hackish way, and partially. Distributed revision control systems out there: Mercurial[1] (I've used it, works great), Bazaar-ng, Git, etc. This illustratred intro to distributed systems[2] will be of help understanding the differences. Roberto [1] http://www.selenic.com/mercurial/wiki/ [2] http://betterexplained.com/articles/intro-to-distributed-version-control-illustrated/ -- http://blog.divisiblebyfour.org/ _______________________________________________ UPHPU mailing list [email protected] http://uphpu.org/mailman/listinfo/uphpu IRC: #uphpu on irc.freenode.net
