From: Vladimir Prus (ghost_at_[hidden])
Date: 2003-03-21 05:34:30
> Boost needs some form of issue tracker to get ready for releases. It will
> be interesting to see how using the WIKI for this works out.
> Thanks for experimenting:-)
Here's what I think about possible alternatives
- Wiki just won't work. It misses minimal functionality: you can't attach
patch to an issue, add comment, view history. The most important problem
is that there's no notification mechanism. You can't declare issue fixed and
then let the origian reporter reponed it, if needed, for example. You also
can't search for issues -- that's important problem too.
For Boost.Build, Wiki just lists a few most important issues, and ones that
are not classified yet. I don't think that putting 100 issues to Wiki is
- Sourceforge tracker is not good. I've abondoned all hope after finding that
it cannot even do text search on issue description.
- Scarab, the tool I was trying to use, work fine for me. Alghough it has some
bugs. I don't know what's the current state is: I'm running an old version
and was scared to use CVS head back then, but a lot of resources was put into
development recently. Maybe it got better.
- Bugzilla is mature. I don't have any experience with it, though. Some folks
are going to experiment with it at my work just now; I'll watch how it goes.
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk