The latest developments have a bunch of anti-spam measures. The r3432
revision from Trac trunk is actually running on projects.edgewall.com
itself, so it should be quite stable. If you have a little patience,
there should probably be a 0.10 beta quite soon.
No matter whether and when we update - the bad thing has happened and we
already have a database full of spam (no backups without spam available).
We have to find a general way of cleaning it up.
The nice thing of the theoretical way I put up is that I am able to
delete all changes that are spam - with or without comments.
Are there any ideas how to expand ticket and ticket_change to a
ticket_state table?
Kind regards:
al_shopov
_______________________________________________
Trac mailing list
[email protected]
http://lists.edgewall.com/mailman/listinfo/trac
