Re: Summary of XEmacs Issue Tracking System Issues
Mike Kupfer writes:
I was thinking that it might help dissuade someone who wasn't
particularly motivated to cause us grief. I don't know if there's a
configuration option for this in RoundUp or not.
OK, I'll check. I still don't think it's likely to be very useful.
Speaking of email, I'm on the nosy list for issue298, but I
don't recall
getting any email when it was closed on the 23rd (I just got the weekly
summary email). That doesn't seem right.
It's not. I'll see what I can do, but it may take a while. Debugging
mail problems sucks. :-)
All I know is that we routinely got spam postings in the
opensolaris.org
forums, and I was told that they were aimed at raising the spamming
site's ranking in search results.
OK, that makes sense, of a certain rather disgusting kind.
I didn't mean to suggest disabling indexing. I'm just saying
that if we
add some sort of automated spam detection, new attachments should be
scanned, too (if possible).
Python's Roundup seems to have this. Someday soon I'll see about
adding it.
> They are all still valid as far as I know.
Well, issue53 was marked committed before it was closed (with Reason
left unset). So yes it was a valid issue, but does it need to be
reopened?
Yes. There are still open tasks in that issue. They could be moved
to separate issues, but probably almost nobody but me cares how
tracker issues are organized.
A similar comment applies to issue634.
Adrian's last comment was that the new behavior is arguably a
regression. It doesn't *need* to be open, but it probably is better
left open until somebody who can judge does judge.
On the bright side of all this, I've learned a bit about SQL. :-)
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta