> That doesn't make any sense since a fixed bug would be closed. Not until after time is spent trying to reproduce/understand the bug. If you know when it was last seen, you can confirm that you are triggering it correctly, but that it no longer exists in the current version.
>> interpretation, updating the version is a mark that you've tested it >> in a newer version and that the problem still exists as described. > > That doesn't add any information but it rather removes information (in > what version the bug was first found). I wasn't aware that Trac was in the habit of discarding old information. In fact, I get the distinct impression that it specifically states "version changed from 1.0 to SVN." in the change history, and that this would be easy to locate with your browser's in-page search function. -FM -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
