I've noticed a lot of people lately updating the trac version field of to be more recent. For example changing version from 1.0 to 1.2 or 1.1 to SVN. I thought this field was supposed to track the version against which a problem was written -- that is, the version of code in use by the reporter of the problem. When that is what is kept in the field, then version can be somewhat useful as an indication of (at least) how long a problem has been around. It's not perfect -- someone might be using 1.2 and notice a problem that has been around since day 1, but it is something.
I'm not sure why people are feeling it is necessary or helpful to change this field? If a ticket was opened against version 1.1 and is still open, then we can reasonably assume that it's still a problem in 1.2 and current SVN. (If it is not, then the ticket should just be closed as fixed.) It's not necessary to update the version to reflect that an old still-open problem is still present in current trunk, and I see this kind of update as generally unhelpful since we lose easy access to the information that the problem is in fact long-standing and not newly-introduced. I find having some sense of hold old a problem is to be helpful when looking at fixing it, since if it is in fact new I'll probably try to figure out what has changed to cause the breakage whereas if it's been around forever I know that sort of investigation is not likely to be helpful. I don't see any place in the contributing doc that mentions what version is supposed to be set to, so perhaps my understanding of what it is supposed to be is just wrong. So I figured I'd post here and ask: what do others view as the purpose of this field? Karen -- 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.