When you write of standalone version control systems, do you mean using svn/hg/git out of the box, and developing all the other software for our needs? If not, what examples of standalone VCS are you writing about? -- Greg On Sun, Jan 29, 2012 at 04:21:03PM -0700, Lee Passey wrote:
On 1/27/2012 5:22 PM, Greg Newby wrote:
That's why I tried TRAC. It uses subversion rather than git or hg, but the core capability of branches, hierarchies, etc. seemed a good fit for our purposes.
At your instigation I went out to the TRAC web site and looked at this product.
TRAC is an integrated project management tool, not merely a Version Control System. In fact, TRAC is not a VCS at all, it is merely provides a front end to Subversion, and apparently through the use of plugins to git and Mercurial as well.
TRAC has a number of attractive features that would be useful to project WOPR, including a bug tracking system, a wiki, and an RSS feed.
However, I don't see a current need for the full suite that TRAC offers. Because TRAC is not a VSC, but only a portal into a VCS, I think that the right thing to do at this point is to install a stand-alone VCS with an eye towards integrating it into TRAC at some future point. For our purposes, I think just about any concurrent version system would be adequate, so you should pick the one that you think would be easiest to administer. _______________________________________________ gutvol-d mailing list gutvol-d@lists.pglaf.org http://lists.pglaf.org/mailman/listinfo/gutvol-d