Hello, Thanks to all who tested the branch and provided feedback! In particular, thanks to the feedback from Peter, I reorganized the migration document (*) so that it starts with some examples, continues with the changes needed in the Python code (+ since today a section about i18n for plugins), before finishing with the changes needed in the templates. I hope things are clearer this way and a bit more engaging to read.
I think the branch is now in good enough state to be merged on trunk. At which point we could encourage people to migrate their plugins as well, get some more feedback and polishing done, and release 1.3.2 shortly after (mid- to end of February). So if there's no objections, I'll proceed with the merge later this week. On a related note, the restyling changes which are also demonstrated on t.e.o/testing jointly with the Jinja2 branch may or may not be ready for 1.3.2 as well, for now they'll stay on +testing. Once the Jinja2 merge is done, I'll rebase the wiki-restyling branch on trunk and start to make use of the Jinja2 engine to generate the .css (statically). -- Christian (*) https://trac.edgewall.org/wiki/TracDev/PortingFromGenshiToJinja -- You received this message because you are subscribed to the Google Groups "Trac Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to trac-dev+unsubscr...@googlegroups.com. To post to this group, send email to trac-dev@googlegroups.com. Visit this group at https://groups.google.com/group/trac-dev. For more options, visit https://groups.google.com/d/optout.
