Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>We looked at TFS, but ended up going with Subversion + Trac + VisualSVN. We don't do CI right now but Cruisecontrol would be what we'd use, I think. </p> <p>I started using Trac with numerous open-source projects, and it's a great. It's really only a portion of what TFS does, so you'll have to make a decision there -- if you use everything, TFS probably does a better job of tying it all together. Trac is a wiki/bug tracker/source browser. Everything is linked - when you type in the name of a WikiPage or say "Fix bug #1234" in a commit message, whenever you see that message in Trac the links go to the right places. It is tool that helps you do your job and but stays out of the way, generally. </p> <p>VisualSVN is a great bridge between TortoiseSVN (a Subversion client) and VisualStudio, and greatly improves productivity. They have a free trial, and it's not very expensive afterwards ($50/user), but well worthwhile.</p> <p>One possible downside to Trac is in a Windows world, it is a pain to get working on IIS. I've installed Trac many times, but got frustrated quickly trying to get it working properly. I ended up installing Apache on a different IP (could also use different port) and then it was seamless. </p> <p>Except for one person on my team (who had a tiny bit of experience), no one had ever used subversion before. A couple had used VSS, and thats all. Everyone was pretty skeptical, but I'd say within a few days they were all converts. After fully learning Trac and getting used to everything (a few days more), everyone is totally sold and loves it.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload