The data model has not changed much, so that criticism is still relevant.
The templating engine has been switched again (ClearSilver -> Genshi -> Jinja). I don't know if you refer to the first or the second switch. I also don't know if this was an improvement or just even more churn.
Lack of Milestone customization: I'm not sure I understand.
Poor performance: How many tickets do you have?
Glad to hear that! Running an open project is hard.
> [...] switched again (ClearSilver -> Genshi -> Jinja)
Genshi was current when I used it; I wasn't aware it had switched to jinja (or it slipped my mind by now..)
> Lack of Milestone customization: I'm not sure I understand.
Back then, there were no custom fields for milestones, and the code didn't make it easy to do. Of course, this means you need changes to search facilities, and any other parts of the codebase. I had to write that also, and the target workflow was not at all complex.
As for the performance, we had about 20k tickets and 2k milestones when the system was replaced. By then it had been completely unusable for a long time.
Honestly, the only positives I have to say about Trac concern real-world usage by a hacker. Once you've learned it, and hacked it to your liking, it's very productive. But to get to that point, it's a sixty feet tall stack of ugly hacks, and frankly I would not recommend it to anyone...
Again to be clear, I did not look at the trac repo in many years, nor do I intend to.
I see. Milestones still have no custom fields. Did you ever send your customizations upstream?
Very hard to find the time to upstream something like that when you are on a limited budget in the first place..