Stavros Macrakis <stavros.macrakis <at> verizon.net>
2003-01-02 05:31:42 GMT
Happy New Year to everyone!...
The bug database at sourceforge is getting pretty unwieldy.
It's getting to the point that when I run into a bug, it is not trivial
to check whether it's already been reported. After all, there are >200
in the database (including both current and closed ones). It would be
nice if we could categorize bugs somehow, or even do freetext search on
them. Any ideas for this? Should we introduce more categories? For
example, we could categorize by subsystem: general simplifier (simp,
csimp), rational function package (ratXXX), taylor, limit, integrate,
rpart, etc. Obviously users who don't look at the internals aren't
usually going to be able to correctly assign categories like this, but I
don't think many such users submit bug reports and maintainers can
always correct the category field later. Or is there a better tool?
Also, I notice that no bugs have been declared Closed for over two
months. Is that because bug-fixing is on hold while the new release is
being prepared? Or because people are busy doing other things? Or
because bugs are being fixed in source but not closed? As I understand
it, our criterion for "closed" is that a fix has been put in source and
checked/tested by the person who applied it, right? Do we do (or plan
to do) any sort of regression testing, making sure that previously
closed bugs don't reappear?