On 11/04/13 09:51, Joe Dreimann wrote:
No objection to that.
Two questions:
1) Was it the error report that got the user to think it is a Trac problem? Do
we need to amend this?
Given the text "While doing a GET operation on /admin/accounts/users,
Trac issued an internal error." it looks like we have missed some places
to specify that it is an error with bloodhound.
2) Should we encourage people using bloodhound to raise all issues to us (incl
likely Trac ones)?
I would say yes to the second one because so far we've always kept tickets like
that open as a reference and raised one upstream. For users that makes our site
a single point of contact, and we know what it is upstream that affects them.
Yes. By definition these are issues for Bloodhound regardless of whether
it is in Trac, bloodhound or plugins that we include.
Cheers,
Gary
