On 10/13/2011 3:55 PM, Les Mikesell wrote:
Isn't there a better place to recommend sending the error report than
a user's mail list?
The project has decided long ago to filter problem reports on the
users mailing list. There are several reasons for this.
See the big yellow box at http://subversion.tigris.org/issue-tracker.html
I can understand verifying that some unusual/questionable behavior is
really a bug, but when the program itself generates an exception
report there is not much question that it is a bug and not something
other users can help with - devs, maybe.
From the volume and mixed quality of reports, I'm guessing you don't
want this kind of stuff going straight to dev@. But as mentioned, there
also isn't much that other users can do about it.
So I guess, what's the goal? Probably it's that someone (likely a dev)
will look at all the reports coming in, maybe email back to a couple of
the senders to get more details, then eventually add new issues as
appropriate. Some kind of human filtering mechanism to distil the raw
reports into concrete issues.
bugreports@s.a.o?
-Mike
PS. It seems kind of unfortunate that stack traces aren't included in
the reports. I'd guess that that would help you figure out what's going
on better than relying on users to put in a useful text description
about what they were doing at the time...
