Hi,
There are reports in the pharo tracker that are not solvable because
the software the bug
is reported about is not part of pharo.
I wonder if that makes sense... from the bug-fixing of Squeak, I have
found that it's very
important to keep the numner of open issues as small as possible. (the
nearly 1000 open reports
they gatheres when doing 3.10 in Squeak is completely unmanagable, for
example).
I would suggest to put these reports on a wiki page, instead of the
bugstracker. Or report them
to the developers of the package.
Marcus
--
Marcus Denker -- [EMAIL PROTECTED]
http://www.iam.unibe.ch/~denker
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
