Opened 17 months ago
Last modified 3 days ago
#18092 new task
Upgrade to Trac 1.4
| Reported by: | stoecker | Owned by: | stoecker |
|---|---|---|---|
| Priority: | normal | Milestone: | Longterm |
| Component: | Trac | Version: | |
| Keywords: | Cc: |
Description (last modified by )
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
Attachments (0)
Change History (20)
comment:1 Changed 17 months ago by
| Component: | Wiki content → Trac |
|---|---|
| Owner: | changed from team to stoecker |
comment:3 Changed 17 months ago by
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.
comment:4 Changed 17 months ago by
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.
comment:5 Changed 14 months ago by
| Milestone: | 19.11 → 19.12 |
|---|
comment:6 Changed 13 months ago by
TODO:
- change site.html to new format: https://trac.edgewall.org/wiki/TracInterfaceCustomization#SiteAppearance
comment:7 Changed 13 months ago by
| Description: | modified (diff) |
|---|
comment:8 Changed 13 months ago by
| Description: | modified (diff) |
|---|
comment:9 Changed 13 months ago by
| Description: | modified (diff) |
|---|
comment:10 Changed 13 months ago by
| Description: | modified (diff) |
|---|
comment:11 Changed 13 months ago by
| Description: | modified (diff) |
|---|
comment:12 Changed 13 months ago by
| Milestone: | 19.12 → 20.04 |
|---|
Lots of work and little benefit.
Let's hope situation get's better.
comment:14 Changed 13 months ago by
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 :-)
comment:15 Changed 9 months ago by
| Milestone: | 20.04 → Longterm |
|---|
May I move this to the longterm goals?
comment:17 follow-up: 18 Changed 3 days ago by
- Any updates? Is this really that much work? https://trac.edgewall.org/wiki/TracUpgrade
- Well if going Trac 1.4 is so much work can we at lest get Trac 1.2.6 (latest stable)?
comment:18 Changed 3 days ago by
Replying to anonym:
- 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.
- 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.
comment:20 Changed 3 days ago by
| Description: | modified (diff) |
|---|
Ooops, wrong component :-)