I find the mail interface is easiest for bug submissions. It seems to work fast, and you get a auto-response email.
| [reply] |
I have used Request Tracker in the past. At a previous employer there were two installs of RT. We noticed that RT, at that time, did not scale well. As the database became larger it would become unresponsive. We were never able to determine the exact cause but I think there are several. For example, RT would not remove old session IDs from its table. This caused the database to have query tens of thousands of session IDs whenever a page was loaded. I created a script that would remove old sessions but performance was only marginally better. I can only hope that newer RT code has been improved.
| [reply] |
Being a pretty heavy user of Perlbug, the early version 3 RT's did react slowly at times. However, since Perlbug was updated to RT 3.6, the performance has been noticeably better, especially for searches.
Test your modules with bleadperl!
rsync -avz rsync://public.activestate.com/perl-current/ .
./Configure -des -Dusedevel -Dprefix=/path/to/test/perl
make test
make install
Now, please test you modules! If you have test failures that don't happen with Perl 5.8.8, send a simplified test case to perlbug at perl.org
| [reply] |
Have you tried reporting this to Jesse / Best Practical? Maybe the server ain't up to the job. Maybe it's being DoSed or spam attacked. Maybe you'll get a better response outside peak times.
I have also had intermittent service on rt.cpan.org, with 500 response to queries following an update post.
--
Oh Lord, won’t you burn me a Knoppix CD ?
My friends all rate Windows, I must disagree.
Your powers of persuasion will set them all free,
So oh Lord, won’t you burn me a Knoppix CD ?
(Missquoting Janis Joplin)
| [reply] |