Slashdot Mirror

We use CVSTrac, and it serves our purposes very well. It's not PHP/MySQL, it's SQLite-based, and is written in C, but to me, that just makes it easier to support -- there is one native process, so just one point of failure, no DB servers to monitor (yet, the data is available in a SQL DB), no web servers to configure (though you can set it up with an external webserver if you wish).

It is free, well-documented and is actively developed. It was written by the same guy who wrote SQLite.

It is also self-hosting, which means that the CVSTrac project uses CVSTrac for issue tracking, so you can go to http://www.cvstrac.org/cvstrac/ and get a good idea of how the system works without ever installing it.

We use CVSTrac, and it serves our purposes very well. It's not PHP/MySQL, it's SQLite-based, and is written in C, but to me, that just makes it easier to support -- there is one native process, so just one point of failure, no DB servers to monitor (yet, the data is available in a SQL DB), no web servers to configure (though you can set it up with an external webserver if you wish).

It is free, well-documented and is actively developed. It was written by the same guy who wrote SQLite.

It is also self-hosting, which means that the CVSTrac project uses CVSTrac for issue tracking, so you can go to http://www.cvstrac.org/cvstrac/ and get a good idea of how the system works without ever installing it.

If you're a small team you may want to keep it simple, CVSTrac is simple, it's written in that unsafe language we call C. Despite a recent DOS/SQL injection vuln, I'd still be more comfortable running this than Mantis (A glimpse at a few files in CVS was enough for me to avoid running Mantis any time soon).

Long before Trac for Subversion, there was CVSTrac for CVS. It's a little more austere, but offers the same features: integrated wiki, CVS change tracker, CVS browser, and trouble tickets. CVSTrac now can be compiled to support Subversion.

FitNesse combines a Wiki with an acceptance testing tool. Tables on Wiki pages hold test data and expected outputs; click the "test" button and FitNesse runs your application with the test data and checks the results against the expected values (similar to JUnit and others). Although written in Java, FitNesse also can test Python, Ruby, C++, .NET, Smalltalk, and Perl applications. FitNesse builds on Fit, the Framework for Integrated Testing by Ward Cunningham, the creator of the original Wiki.

Ward also was the first person to integrate source code into a Wiki. In his WikiBase , Ward presents the source code for his original Wiki on Wiki pages containing HyperPerl, a Perl implementation of Literate Programming. This may not suit current development needs, but it is fascinating.

My employer produces a large-ish software package, with 10 years of history and a small, 2-3 people, development team. Since I joined we have made massive strides in automating the build process, include some unit tests, and a few smoke tests in an automated process.

Well, the effort paid off. Before we supported one version of HP/UX, and one release of Linux, now we support HP/UX (still a pain), and 4 looking at going to 6 Linux version/distributions and it is less work to produce a release now than ever just a year ago.

Tools like automake, autoconfig, libtool, cvstrac and of course cvs have made my life bearable.

The OP said they think svn is overkill for what they want. Personally I think of svn as CVS II, and expect many people to migrate eventually (probably about the same speed as migration from Apache 1 to Apache 2).

The CVSTrac features are really nice, especially if you want to show a PHB what is going on, ro have them actually participate. For example, see the timeline feature. Having all your CVS checkins, wiki and bug tracker items combined is really nice.

I would recommend using CVS and CVSTrac. They both work fine under Windows (as servers). CVSTrac also gives you the benefit of browsing the code from the web, a bug tracker and a Wiki.