Upgrade to Trac 1.6 when released

[stoecker]

Trac 1.4 was released. Upgrade should be done after waiting some time first the bugs to settle after a major version upgrade.

• Change site html to new format ​https://trac.edgewall.org/wiki/TracInterfaceCustomization#SiteAppearance
• switch plugins to 1.4 branches
• iniadminpanel plugin wont work, as the Genshi support seems broken in a major way: ​https://trac.edgewall.org/ticket/13237 - update plugin to get it work, still needs a proper Jinja update for real 1.4 support
• Add a modified CSS to get an acceptable layout back.
• Check if JOSMs simple minded wiki parser survives the layout changes

[stoecker]

Ooops, wrong component :-)

[Klumbumbus]

I hope the translation is included properly this time :)

[Don-vip]

1.4 looks very promising:

• Switch to Jinja2 template engine for faster and more memory lenient server-side content generation
• 5 times speed-up when rendering query results, thanks to the migration from Genshi to Jinja2.

Maybe we should nevertheless try this version on another machine, to make sure all bugs impacting us are properly identified and fixed in the next maintenance update. Otherwise I fear some bugs could remain undetected until we switch.

[stoecker]

That "Genshi to Jinja2" was actually the reason why I went away from Trac mailinglists. They wanted to drop Genshi without a time when both are supported and I voiced the opinion that this is the worst sign you can sent to plugin authors. And instead of reacting on what I said they started to blame me for the way I said it (which was relatively harmless, I do worse when really upset :-).

Regarding the speedup: I don't think you will notice it. E.g. everything which is slow in our wiki (like the translation tables) neither uses Genshi nor Jinja and the main speed issue is database access and client side rendering, not the content generating.

[stoecker]

TODO:

• change site.html to new format: ​https://trac.edgewall.org/wiki/TracInterfaceCustomization#SiteAppearance

[stoecker]

Lots of work and little benefit.

Let's hope situation get's better.

[Don-vip]

Why so late? Are you waiting for a new Trac release?

[stoecker]

I either hope that the workload gets reduced or that there comes up a reason why we should upgrade (i.e. a wonderful new feature :-)

[simon04]

May I move this to the longterm goals?

[stoecker]

Ticket #20382 has been marked as a duplicate of this ticket.

[anonymous]

1. Any updates? Is this really that much work? ​https://trac.edgewall.org/wiki/TracUpgrade

2. Well if going Trac 1.4 is so much work can we at lest get Trac 1.2.6 (latest stable)?

[stoecker]

Replying to anonym:

1. Any updates? Is this really that much work? ​https://trac.edgewall.org/wiki/TracUpgrade

A lot. I did this for 2 other (less intensively used) instances and it took some time.

2. Well if going Trac 1.4 is so much work can we at lest get Trac 1.2.6 (latest stable)?

I think so. Have to check.

[stoecker]

There was trouble with trac 1.2.x upgrade as well: See #16651

[stoecker]

Seems trac 1.6 will finally have python 3 support, so that's the next logical step for update. I'd think we skip 1.4 completely.

​https://trac.edgewall.org/wiki/TracDev/ReleaseNotes/1.6

[anonymous]

Quite some time has passed and trac 1.6 is nowhere to be seen. Can we reapproach the question of updating to 1.4.3 or at least 1.2.6?

[gaben]

Python 3.5+ compatibility added with ​Trac 1.5.3.

[stoecker]

Replying to gaben:

Python 3.5+ compatibility added with ​Trac 1.5.3.

I know. There are already people officially using the devel version instead of the release. Probably that's really the way forward.