On 11.07.2007 00:26, Felix Knecht wrote:
Of course: Because the issue is marked for versions 2.1.10,2.1.9, 2.1.8, 2.1.7, 2.1.6 as well. Somebody seemed to have fixed it for 2.1.11-dev and I did it for 2.2-dev. But all the other versions are still open. That's why I didn't closed it.
That seems to be a misunderstanding. We don't fix versions (they are "locked" anyway), we only fix branches. (Unless there is a major security issue for which me might branch a particular release and only fix this issue on this additional branch.) Usually if an issue has been fixed on all active branches the issue can be closed.
Joerg
