Hi, Chris. In the SAC project (www.sac-home.org), we're using Subversion as our source code repository and Bugzilla as the bug tracking mechanism. Both work, IMO, quite well.
Subversion makes it trivial to go back and rebuild software as it on date X, so fault isolation of late-appearing performance problems, etc., is straightforward. Here's an example of the revision history from sac2c: ------------------------------------------------- [EMAIL PROTECTED]:~/sac2c> svn log |more ------------------------------------------------------------------------ r15582 | sah | 2007-08-23 11:52:26 -0400 (Thu, 23 Aug 2007) | 2 lines fixed an accesss to freed memory ------------------------------------------------------------------------ r15581 | ktr | 2007-08-22 11:33:31 -0400 (Wed, 22 Aug 2007) | 2 lines The standard library can now be compiled with -ecc -check c -dosaa. However, when compiling classes/random/Rand.sac, a global object appears in an aftergu ard. This then kills MMV. Since I have no idea how global objects should be handled wr t constraint checks, I would like someone else to have a look at it. ------------------------------------------------------------------------ r15580 | ktr | 2007-08-22 08:33:42 -0400 (Wed, 22 Aug 2007) | 1 line Dynamic constraint checking. Hooray. -------------------------------------------------------- If I wanted to rebuild my sac2c compiler as of revision r15582, I'd merely do: svn update -r r15582 make To bring it back up to date and/or to pick up recent changes, I'd do: svn update . make Subversion facilitates multiple ongoing projects for one user, so you don't tend to get screwed by BillWare(tm) as you do with SourceHaHaHaSafe. You can compare revisions, etc., with ease. Bugzilla is fine for any of our work, although it's a bit clunky, I think. Your basic web-based tool. It has reasonable search capabilities, keeps track of open and closed bugs, allows bugs to be reopened, lets people attach test cases and commentary to bug reports, etc. Bob On Fri, 2007-08-24 at 10:16 +0800, Chris Burke wrote: > Sherlock, Ric wrote: > > Through my use of J I have been introduced to Subversion and now use it > > for version control of my own projects. > > > > A co-worker, who I also convinced to go the Subversion route, has in > > turn introduced me to The Trac Project that integrates with Subversion > > and provides "an enhanced wiki and issue tracking system for software > > development projects" > > > > http://trac.edgewall.org/ > > > > It makes the browsing of SVN sites a real pleasure. In addition it adds > > bug tracking, as well as providing a project wiki which I'm finding a > > useful place to document my design ideas etc for a project. There is a > > demo site you can check out at the site. > > I am interested in this, and would appreciate comments from others. > > Right now, our issue reporting is via the forum, wiki and private email, > and this is far from ideal. It is too easy for items to fall through the > cracks, and not easy for users to know if issues have been reported, or > what is their status. On the other hand, the popular issue reporting > systems I have looked at seem to be far too complex for us and so more > trouble than they are worth. We need something simple and useful enough > that we will actually make use of it. I thought that the best solution > would be to write one myself, and link it in with our wiki, but this > Trac system sounds much better. > > ---------------------------------------------------------------------- > For information about J forums see http://www.jsoftware.com/forums.htm ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
